# Magento XPath Injection

Advisory record · `GHSA-h437-qjj9-vmq4`

- **Identifiers:** `GHSA-h437-qjj9-vmq4` · `BIT-magento-2021-21025` · `CVE-2021-21025` · `PKSA-q4sd-rbfw-bn9m` · `PKSA-vf7x-93bd-9dxz`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-91](https://cwe.mitre.org/data/definitions/91.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.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.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `magento/community-edition` (Packagist): affected `<2.3.6-p1 || >=2.4.0, <2.4.1-p1`; fixed in `2.3.6-p1`, `2.4.1-p1`
- `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.1-p1 are affected by an XML injection flaw in product layout updates. An authenticated attacker with access to the admin console could exploit it to run arbitrary code. Upgrade magento/community-edition to 2.3.6-p1 or 2.4.1-p1. No fixed version is listed for magento/project-community-edition, which is affected through 2.0.2.

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

- 9.1 Critical, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`, from CNA (adobe)

- **CISA KEV:** Not listed.
- **EPSS:** 0.032, the 88th percentile, on 19 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-h437-qjj9-vmq4)

## Sources

- [GitHub Advisory Database: GHSA-h437-qjj9-vmq4](https://github.com/advisories/GHSA-h437-qjj9-vmq4)
- [OSV: GHSA-h437-qjj9-vmq4](https://osv.dev/vulnerability/GHSA-h437-qjj9-vmq4)
- <https://nvd.nist.gov/vuln/detail/CVE-2021-21025>
- <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-h437-qjj9-vmq4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h437-qjj9-vmq4/>. Everything for agents: <https://agentprime.io/llms.txt>.
