Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

SQL Injection in DjangoGHSA-xpfp-f569-q3p2

CRITICALFix: django/django@0bd57a8

GHSA-xpfp-f569-q3p2 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in django. 5 public exploit references exist, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.

Also known asBIT-django-2021-35042CVE-2021-35042PYSEC-2021-109
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
5 known
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
44.4%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
30.4%53.6%76.8%100.0%90.0%44.4%Apr 26Sep 26Oct 26

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

How urgent is this, really

GHSA-xpfp-f569-q3p2 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
🐍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

Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjango≥ 3.2a1&&< 3.2.53.2.5pip install --upgrade 'django==3.2.5'
🐍PyPIdjango≥ 3.0a1&&< 3.1.133.1.13pip install --upgrade 'django==3.1.13'

Affected Products

2 products · 3 configurations
Application
djangodjangoproject
≥ 3.2 && < 3.2.5
range
OS
fedorafedoraproject
1 version
34
Exploits & PoCs
5

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

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update django to 3.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xpfp-f569-q3p2 is resolved across your whole dependency graph.

  3. 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
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-xpfp-f569-q3p2 (CC BY 4.0)

Frequently Asked Questions

Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application.
O3 Security · Impact-Aware SCA

Is GHSA-xpfp-f569-q3p2 in your dependencies?

Find it across PyPI, including transitive dependencies.

SQL Injection in Django (Critical 9.8)