How severe is GHSA-2gwj-7jmv-h26r?

GHSA-2gwj-7jmv-h26r has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2gwj-7jmv-h26r?

GHSA-2gwj-7jmv-h26r affects the following packages: django (PyPI), django (PyPI), django (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-2gwj-7jmv-h26r?

Update django to 2.2.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2gwj-7jmv-h26r is resolved across your whole dependency graph.

How do I detect GHSA-2gwj-7jmv-h26r in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2gwj-7jmv-h26r if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-2gwj-7jmv-h26r actively exploited in the wild?

Yes. There are 3 known exploit references for GHSA-2gwj-7jmv-h26r, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-2gwj-7jmv-h26r?

GHSA-2gwj-7jmv-h26r has an EPSS (Exploit Prediction Scoring System) score of 18.7%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-2gwj-7jmv-h26r?

GHSA-2gwj-7jmv-h26r 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-2gwj-7jmv-h26r published, and has it been updated?

GHSA-2gwj-7jmv-h26r was published on April 13, 2022 and was last updated on February 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

SQL Injection in DjangoGHSA-2gwj-7jmv-h26r

CRITICALFix: django/django@2044dac

GHSA-2gwj-7jmv-h26r is a critical-severity (CVSS 9.8) SQL Injection vulnerability in django. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.

Also known asBIT-django-2022-28346CVE-2022-28346PYSEC-2022-190

Published

Apr 13, 2022

Updated

Feb 21, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

3 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

18.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐍django🐍django🐍django

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

Description

An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. QuerySet.annotate(), aggregate(), and extra() methods are subject to SQL injection in column aliases via a crafted dictionary (with dictionary expansion) as the passed **kwargs.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django`	≥ 2.2&&< 2.2.28	2.2.28`pip install --upgrade 'django==2.2.28'`
🐍PyPI	`django`	≥ 3.2&&< 3.2.13	3.2.13`pip install --upgrade 'django==3.2.13'`
🐍PyPI	`django`	≥ 4.0&&< 4.0.4	4.0.4`pip install --upgrade 'django==4.0.4'`

Affected Products

2 products · 5 configurations

debian linuxdebian

2 versions

9.011.0

Application

djangodjangoproject

≥ 4.0 && < 4.0.4

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, …

github.comGithubApr 2022

Report on github.com

github.comGithubMay 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django to 2.2.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2gwj-7jmv-h26r is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat OpenStack does ship the affected version of Django, however, vulnerability is not exposed in the product as it does not make use of vulnerable code. We may update Django in a future release of OpenStack.

Product	Fixed in	Advisory
Red Hat Ansible Automation Platform 2.1 for RHEL 8	`automation-controller-0:4.1.2-2.el8ap`	RHSA-2022:5702
Red Hat Automation Hub 4.2 for RHEL 7	`python3-django-0:2.2.28-1.el7pc`	RHSA-2022:5703
Red Hat OpenStack Platform 16.1	`python-django20-0:2.0.13-18.el8ost`	RHSA-2022:8872
Red Hat OpenStack Platform 16.2	`python-django20-0:2.0.13-17.el8ost`	RHSA-2022:5115
Red Hat Satellite 6.11 for RHEL 8	`python-django-0:3.2.13-1.el8pc`	RHSA-2022:5498
RHUI 4 for RHEL 8	`python-django-0:3.2.13-2.el8ui`	RHSA-2022:5602

Frequently Asked Questions

An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. `QuerySet.annotate()`, `aggregate()`, and `extra()` methods are subject to SQL injection in column aliases via a crafted dictionary (with dictionary expansion) as the passed `**kwargs`.

O3 Security · Impact-Aware SCA

Is GHSA-2gwj-7jmv-h26r in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works