# Magento Improper Access Control leads to Security feature bypass

Advisory record · `GHSA-vhcq-4xrm-2cr2`

- **Identifiers:** `GHSA-vhcq-4xrm-2cr2` · `CVE-2025-27191` · `PKSA-j33z-72k7-nwyn` · `PKSA-x76v-gf6x-15jx`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 8 Apr 2025
- **Updated:** 23 Oct 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Apr 2025, 21:31 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-p5 || >=2.4.6-p1, <2.4.6-p10 || >=2.4.5-p1, <2.4.5-p12 || <2.4.4-p13 || >=2.4.8-beta1, <2.4.8-beta2 || =2.4.5 || =2.4.4 || =2.4.6 || =2.4.7`; fixed in `2.4.7-p5`, `2.4.6-p10`, `2.4.5-p12`, `2.4.4-p13`, `2.4.8-beta2`

## 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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0051, the 44th percentile, on 20 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-vhcq-4xrm-2cr2)

## Sources

- [GitHub Advisory Database: GHSA-vhcq-4xrm-2cr2](https://github.com/advisories/GHSA-vhcq-4xrm-2cr2)
- [OSV: GHSA-vhcq-4xrm-2cr2](https://osv.dev/vulnerability/GHSA-vhcq-4xrm-2cr2)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-27191>
- <https://github.com/magento/magento2>
- <https://helpx.adobe.com/security/products/magento/apsb25-26.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-vhcq-4xrm-2cr2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vhcq-4xrm-2cr2/>. Everything for agents: <https://agentprime.io/llms.txt>.
