# Magento 2 Community Edition Security Bypass

Advisory record · `GHSA-p9vf-4jx2-5hpp`

- **Identifiers:** `GHSA-p9vf-4jx2-5hpp` · `CVE-2019-8112` · `PKSA-d4pg-bzsk-tptc` · `PKSA-hs2x-xp4v-hmg9`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-345](https://cwe.mitre.org/data/definitions/345.html)
- **Tags:** [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md)
- **Published:** 24 May 2022
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

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

## Affected packages

- `magento/community-edition` (Packagist): affected `>=2.2.0, <2.2.10 || >=2.3.0, <2.3.2-p1`; fixed in `2.2.10`, `2.3.2-p1`

## Machine-written summary

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

> Magento 2 Community Edition versions 2.2.0 through 2.2.9 and 2.3.0 through 2.3.2 (before 2.3.2-p1) are affected by a security bypass. An unauthenticated attacker can get around the email confirmation step for new accounts by using a GET request that captures account data from a POST response during user creation. Upgrade to 2.2.10 or 2.3.2-p1, or later.

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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

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

## Timeline

- 31 Oct 2026, 14:31 UTC: First seen by agentprime
- 31 Oct 2026, 14:31 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-p9vf-4jx2-5hpp)

## Sources

- [GitHub Advisory Database: GHSA-p9vf-4jx2-5hpp](https://github.com/advisories/GHSA-p9vf-4jx2-5hpp)
- [OSV: GHSA-p9vf-4jx2-5hpp](https://osv.dev/vulnerability/GHSA-p9vf-4jx2-5hpp)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-8112>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-8112.yaml>
- <https://github.com/magento/magento2>
- <https://magento.com/security/patches/magento-2.3.3-and-2.2.10-security-update>
- <https://web.archive.org/web/20220121051105/https://magento.com/security/patches/magento-2.3.3-and-2.2.10-security-update>

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-p9vf-4jx2-5hpp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p9vf-4jx2-5hpp/>. Everything for agents: <https://agentprime.io/llms.txt>.