# Magento path traversal vulnerability

Advisory record · `GHSA-fr6f-xmfx-rrpq`

- **Identifiers:** `GHSA-fr6f-xmfx-rrpq` · `BIT-magento-2020-9689` · `CVE-2020-9689` · `PKSA-91z4-mk4h-z382` · `PKSA-vn8z-wfpr-9z9r`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.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:24 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.5-p2`; fixed in `2.3.5-p2`
- `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 (magento/community-edition) versions before 2.3.5-p2 are affected, and magento/project-community-edition versions 2.0.2 and earlier are affected, with no fixed version listed for the latter. A path traversal flaw lets an attacker who can reach the affected software reach files outside intended directories, which the source says could lead to arbitrary code execution. Upgrade magento/community-edition to 2.3.5-p2 or later. The source gives few details on attack requirements, and no fix is listed for magento/project-community-edition.

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

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.041, the 91st percentile, on 20 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-fr6f-xmfx-rrpq)

## Sources

- [GitHub Advisory Database: GHSA-fr6f-xmfx-rrpq](https://github.com/advisories/GHSA-fr6f-xmfx-rrpq)
- [OSV: GHSA-fr6f-xmfx-rrpq](https://osv.dev/vulnerability/GHSA-fr6f-xmfx-rrpq)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-9689>
- <https://github.com/magento/magento2/commit/9436781734e47c83e96977fa770d255217680d5e#diff-7c7399d1d47cdaf120a1a503b7ad87f496d98790203dc82b395ec6bc2d430a55>
- <https://github.com/magento/magento2>
- <https://helpx.adobe.com/security/products/magento/apsb20-47.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-fr6f-xmfx-rrpq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fr6f-xmfx-rrpq/>. Everything for agents: <https://agentprime.io/llms.txt>.
