# Magento sql injection vulnerability

Advisory record · `GHSA-rr59-pjwj-6grj`

- **Identifiers:** `GHSA-rr59-pjwj-6grj` · `BIT-magento-2020-3719` · `CVE-2020-3719` · `PKSA-9s5c-1fbr-kzsg` · `PKSA-q23r-htfp-sg1j`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md)
- **Published:** 24 May 2022
- **Updated:** 6 Mar 2024
- **Reviewed by a person:** No

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

## Affected packages

- `magento/community-edition` (Packagist): affected `>=2.3.0, <2.3.4 || <2.2.11`; fixed in `2.3.4`, `2.2.11`
- `magento/core` (Packagist): affected `<1.9.4.4`; fixed in `1.9.4.4`

## Machine-written summary

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

> Magento community-edition versions before 2.2.11 and from 2.3.0 before 2.3.4 contain an SQL injection vulnerability, and magento/core versions before 1.9.4.4 are affected too. The source does not say what access an attacker needs, but successful exploitation could lead to disclosure of sensitive information. Upgrade magento/community-edition to 2.2.11 or 2.3.4, or magento/core to 1.9.4.4.

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.032, the 88th percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:30 UTC: First seen by agentprime
- 31 Oct 2026, 14:30 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-rr59-pjwj-6grj)

## Sources

- [GitHub Advisory Database: GHSA-rr59-pjwj-6grj](https://github.com/advisories/GHSA-rr59-pjwj-6grj)
- [OSV: GHSA-rr59-pjwj-6grj](https://osv.dev/vulnerability/GHSA-rr59-pjwj-6grj)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-3719>
- <https://github.com/magento/magento2>
- <https://helpx.adobe.com/security/products/magento/apsb20-02.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-rr59-pjwj-6grj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-rr59-pjwj-6grj/>. Everything for agents: <https://agentprime.io/llms.txt>.
