# Magento Cross-Site Request Forgery (CSRF)

Advisory record · `GHSA-w3mq-67mw-3p9f`

- **Identifiers:** `GHSA-w3mq-67mw-3p9f` · `CVE-2018-5301` · `PKSA-hkd6-7s85-q9n9`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 14 May 2022
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

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

## Affected packages

- `magento/community-edition` (Packagist): affected `<2.0.10 || >=2.1.0, <2.1.2`; fixed in `2.0.10`, `2.1.2`

## Machine-written summary

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

> Magento Community Edition versions before 2.0.10 and 2.1.x before 2.1.2 are vulnerable to cross-site request forgery, which can result in deletion of a customer address from an address book. An attacker would need to get a logged-in user to visit a malicious page, which the source does not detail further. Upgrade magento/community-edition to version 2.0.10 or 2.1.2.

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 37th percentile, on 18 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-w3mq-67mw-3p9f)

## Sources

- [GitHub Advisory Database: GHSA-w3mq-67mw-3p9f](https://github.com/advisories/GHSA-w3mq-67mw-3p9f)
- [OSV: GHSA-w3mq-67mw-3p9f](https://osv.dev/vulnerability/GHSA-w3mq-67mw-3p9f)
- <https://nvd.nist.gov/vuln/detail/CVE-2018-5301>
- <https://github.com/magento/magento2>
- <https://magento.com/security/patches/magento-2010-and-212-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-w3mq-67mw-3p9f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-w3mq-67mw-3p9f/>. Everything for agents: <https://agentprime.io/llms.txt>.
