# Magento cross-site request forgery (CSRF) vulnerability via the GraphQL API

Advisory record · `GHSA-h4xc-577p-hgj9`

- **Identifiers:** `GHSA-h4xc-577p-hgj9` · `BIT-magento-2021-21027` · `CVE-2021-21027` · `PKSA-njqv-gp7y-zc74` · `PKSA-nr3b-gd6w-ssxv`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 24 May 2022
- **Updated:** 10 Feb 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 May 2022, 17:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `magento/community-edition` (Packagist): affected `<2.3.6-p1 || >=2.4.0, <2.4.2`; fixed in `2.3.6-p1`, `2.4.2`
- `magento/project-community-edition` (Packagist): affected `<=2.0.2`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Magento community-edition versions before 2.3.6-p1, and from 2.4.0 before 2.4.2, are affected by a cross-site request forgery vulnerability in the GraphQL API. An attacker can lure a logged-in user into a forged request, which could modify that customer's metadata; admin console access is not required. Upgrade magento/community-edition to 2.3.6-p1 or 2.4.2. The source gives no fixed version for magento/project-community-edition, which is listed as affected at 2.0.2 and earlier.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.3 Medium, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`, from CNA (adobe)

- **CISA KEV:** Not listed.
- **EPSS:** 0.016, the 76th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:27 UTC: First seen by agentprime
- 31 Oct 2026, 14:27 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-h4xc-577p-hgj9)

## Sources

- [GitHub Advisory Database: GHSA-h4xc-577p-hgj9](https://github.com/advisories/GHSA-h4xc-577p-hgj9)
- [OSV: GHSA-h4xc-577p-hgj9](https://osv.dev/vulnerability/GHSA-h4xc-577p-hgj9)
- <https://nvd.nist.gov/vuln/detail/CVE-2021-21027>
- <https://github.com/magento/magento2/commit/a2eb7e29ea92a8bbc86c3b6b81b59d8533088497>
- <https://github.com/magento/magento2/commit/a349e022c9ae070e7da262021f9ef182105aa00b>
- <https://github.com/magento/magento2>
- <https://helpx.adobe.com/security/products/magento/apsb21-08.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h4xc-577p-hgj9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h4xc-577p-hgj9/>. Everything for agents: <https://agentprime.io/llms.txt>.
