How severe is CVE-2022-28347?

CVE-2022-28347 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-28347?

CVE-2022-28347 affects the following packages: django (PyPI), django (PyPI), django (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-28347?

Update django to 2.2.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-28347 is resolved across your whole dependency graph.

How do I detect CVE-2022-28347 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 CVE-2022-28347 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 CVE-2022-28347 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-28347 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 is the EPSS score for CVE-2022-28347?

CVE-2022-28347 has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 87th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-28347?

CVE-2022-28347 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 CVE-2022-28347 published, and has it been updated?

CVE-2022-28347 was published on April 12, 2022 and was last updated on October 28, 2026. 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

CVE-2022-28347 — django

CRITICALFix: django/django@00b0fc5

CVE-2022-28347 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in django. A fix is available for django — see the affected versions and patch details below.

SQL Injection in Django

Also known asBIT-django-2022-28347GHSA-w24h-v9qh-8gxjPYSEC-2022-191

Published

Apr 12, 2022

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% 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

A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. This occurs by passing a crafted dictionary (with dictionary expansion) as the **options argument, and placing the injection payload in an option name.

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 · 4 configurations

debian linuxdebian

1 version

11.0

Application

djangodjangoproject

≥ 4.0 && < 4.0.4

range

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 CVE-2022-28347 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, the product is not vulnerable since it does not implement the vulnerable method QuerySet.explain() introduced in Django 2.1.x onward.

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 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

O3 Security · Impact-Aware SCA

Is CVE-2022-28347 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works