# Magento Improper Authorization vulnerability

Advisory record · `GHSA-8w5f-8992-g86j`

- **Identifiers:** `GHSA-8w5f-8992-g86j` · `CVE-2024-39413` · `PKSA-4h72-5zp2-d3d4` · `PKSA-bwdz-tnp6-hk5k`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-285](https://cwe.mitre.org/data/definitions/285.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 14 Aug 2024
- **Updated:** 6 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Aug 2024, 12:35 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `magento/project-community-edition` (Packagist): affected `<=2.0.2`; no fixed version yet
- `magento/community-edition` (Packagist): affected `>=2.4.7-beta1, <2.4.7-p2 || >=2.4.6-p1, <2.4.6-p7 || >=2.4.5-p1, <2.4.5-p9 || >=2.4.4-p1, <2.4.4-p10 || =2.4.7 || =2.4.6 || =2.4.5 || =2.4.4`; fixed in `2.4.7-p2`, `2.4.6-p7`, `2.4.5-p9`, `2.4.4-p10`

## Machine-written summary

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

> Magento Open Source and Adobe Commerce (magento/community-edition) versions from 2.4.4-p1 up to 2.4.4-p10, 2.4.5-p1 up to 2.4.5-p9, 2.4.6-p1 up to 2.4.6-p7, and 2.4.7-beta1 up to 2.4.7-p2 are affected. A low-privileged attacker can bypass security measures and disclose minor information without user interaction. Upgrade magento/community-edition to 2.4.4-p10, 2.4.5-p9, 2.4.6-p7, 2.4.7-p2 or later.

Written 3 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.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`, from CNA (adobe)

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

## Timeline

- 31 Oct 2026, 14:26 UTC: First seen by agentprime
- 31 Oct 2026, 14:26 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8w5f-8992-g86j)

## Sources

- [GitHub Advisory Database: GHSA-8w5f-8992-g86j](https://github.com/advisories/GHSA-8w5f-8992-g86j)
- [OSV: GHSA-8w5f-8992-g86j](https://osv.dev/vulnerability/GHSA-8w5f-8992-g86j)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-39413>
- <https://github.com/magento/magento2>
- <https://helpx.adobe.com/security/products/magento/apsb24-61.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-8w5f-8992-g86j>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8w5f-8992-g86j/>. Everything for agents: <https://agentprime.io/llms.txt>.
