removeItemFromCart mutation modifies cart without authorization

[brettlaishley]

Preconditions and environment

• Magento version 2.4.5-p1

Steps to reproduce

1. From browser and Magento instance
2. Create customer and login
3. Add any product to cart
4. Swap to graphql/altair/postman
5. Use generateCustomerToken mutation to create graphql authorization token
6. Use customerCart query with the authorization token to retrieve details of the user's current cart
7. Take note of the cart_id and cart_item_id
8. Use 'removeItemFromCart` mutation without the authorization token to remove the item from the cart (error received)
9. Return to browser and Magento instance
10. Refresh page to see that supposedly no changes have been made to the cart
11. Add another product to the cart to trigger a more thorough update

Expected result

The cart should have 2 products in it. The 3rd unauthorized mutation should not modify the user's cart. An authorization token should always be required to modify a signed in user's cart.

Actual result

The cart item is removed from the user's cart upon a more thorough cart update from the browser Luma storefront. The removeItemFromCart mutation without an authorization token was still able to modify the user's cart.

Even though the message returned from the API says the "user cannot perform operations on the cart" because the authorization token is not supplied, in the background the item has been removed from the cart.

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @brettlaishley. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[brettlaishley]

@magento give me 2.4.5-p1 instance

[magento-deployment-service]

Hi @brettlaishley. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @brettlaishley, here is your Magento Instance: https://f3f7220149acbdfa56ce81a1a50af0e9.instances.magento-community.engineering
Admin access: https://f3f7220149acbdfa56ce81a1a50af0e9.instances.magento-community.engineering/admin_a354
Login: b0149173
Password: 88a0a329c759

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.

• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[TheRealHunzik]

@magento give me 2.4.5-p1 instance

[magento-deployment-service]

Hi @TheRealHunzik. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @TheRealHunzik, here is your Magento Instance: https://f3f7220149acbdfa56ce81a1a50af0e9.instances.magento-community.engineering
Admin access: https://f3f7220149acbdfa56ce81a1a50af0e9.instances.magento-community.engineering/admin_f0bd
Login: 9cc31e0d
Password: 6ade6f192baa

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://71b042c865ecaab7250dd617cfc1c0bc.instances.magento-community.engineering
Admin access: https://71b042c865ecaab7250dd617cfc1c0bc.instances.magento-community.engineering/admin_fb0c
Login: 00b8a73a
Password: dbbc7121270b