# Magento 2 Community Edition Server-Side Request Forgery vulnerability

Advisory record · `GHSA-33cj-w75f-49m2`

- **Identifiers:** `GHSA-33cj-w75f-49m2` · `CVE-2019-7911` · `PKSA-6mv9-mt5m-rrh3` · `PKSA-d9g6-fdzr-4k86` · `PKSA-qdss-s2b7-s23m` · `PKSA-y44t-k4sh-8b68`
- **State:** Confirmed
- **Severity:** CVSS 7.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 24 May 2022
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

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

## Affected packages

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

## 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.2 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.014, the 73rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 24 May 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-33cj-w75f-49m2](https://github.com/advisories/GHSA-33cj-w75f-49m2)
- [OSV: GHSA-33cj-w75f-49m2](https://osv.dev/vulnerability/GHSA-33cj-w75f-49m2)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-7911>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/magento/magento1ce/CVE-2019-7911.yaml>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/magento/magento1ee/CVE-2019-7911.yaml>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7911.yaml>
- <https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-13>
- <https://web.archive.org/web/20211206084839/https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-13>

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-33cj-w75f-49m2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-33cj-w75f-49m2/>. Everything for agents: <https://agentprime.io/llms.txt>.
