How severe is GHSA-rr59-pjwj-6grj?

GHSA-rr59-pjwj-6grj has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rr59-pjwj-6grj?

GHSA-rr59-pjwj-6grj affects the following packages: magento/community-edition (Packagist), magento/community-edition (Packagist), magento/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rr59-pjwj-6grj?

Update magento/community-edition to 2.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rr59-pjwj-6grj is resolved across your whole dependency graph.

How do I detect GHSA-rr59-pjwj-6grj in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rr59-pjwj-6grj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rr59-pjwj-6grj?

O3 pinpoints whether GHSA-rr59-pjwj-6grj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rr59-pjwj-6grj actively exploited in the wild?

No public exploit code has been indexed for GHSA-rr59-pjwj-6grj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-rr59-pjwj-6grj?

GHSA-rr59-pjwj-6grj is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-rr59-pjwj-6grj published, and has it been updated?

GHSA-rr59-pjwj-6grj was published on May 24, 2022 and was last updated on March 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-rr59-pjwj-6grj

HIGH

GHSA-rr59-pjwj-6grj is a high-severity (CVSS 7.5) SQL Injection vulnerability in magento/community-edition. O3 Security confirms whether GHSA-rr59-pjwj-6grj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Magento sql injection vulnerability

Also known asBIT-magento-2020-3719CVE-2020-3719

Published

May 24, 2022

Updated

Mar 6, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

🐘magento/community-edition🐘magento/community-edition🐘magento/core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Magento versions 2.3.3 and earlier, 2.2.10 and earlier, 1.14.4.3 and earlier, and 1.9.4.3 and earlier have an sql injection vulnerability. Successful exploitation could lead to sensitive information disclosure.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`magento/community-edition`	≥ 2.3.0&&< 2.3.4	2.3.4
🐘Packagist	`magento/community-edition`	all versions	2.2.11
🐘Packagist	`magento/core`	all versions	1.9.4.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update magento/community-edition to 2.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rr59-pjwj-6grj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rr59-pjwj-6grj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rr59-pjwj-6grj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-rr59-pjwj-6grj in your dependencies?

O3 detects GHSA-rr59-pjwj-6grj across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works