GHSA-p64x-8rxx-wf6q is a critical-severity (CVSS 9.8) SQL Injection vulnerability in django. 7 public exploit references exist, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.
Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-p64x-8rxx-wf6q plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
django🐍djangoReal-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 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | ≥ 3.2a1&&< 3.2.14 | 3.2.14pip install --upgrade 'django==3.2.14' |
| 🐍PyPI | django | ≥ 4.0a1&&< 4.0.6 | 4.0.6pip install --upgrade 'django==4.0.6' |
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 3.2 before 3.2.14 and 4.0 before 4.0.6…
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6…
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6…
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6…
Detection & mitigation playbook
Open-source dependencyDetect
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 3.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p64x-8rxx-wf6q 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p64x-8rxx-wf6q can be triaged on real exposure rather than presence alone.
Tailored to GHSA-p64x-8rxx-wf6q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
Applications that constrain the lookup name and kind choice to a known safe list are unaffected. Red Hat Satellite 6 versions include affected versions of python-django, however, the product is not vulnerable since it does not make use of vulnerable functions. Future updates may fix this issue.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Satellite 6.12 for RHEL 8 | python-django-0:3.2.14-2.el8pc | RHSA-2022:8506 |
| RHUI 4 for RHEL 8 | python-django-0:3.2.14-3.el8ui | RHSA-2022:5738 |
Frequently Asked Questions
Is GHSA-p64x-8rxx-wf6q in your dependencies?
O3 Security finds GHSA-p64x-8rxx-wf6q across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.