GHSA-6w2r-r2m5-xq5w is a high-severity (CVSS 7.1) SQL Injection vulnerability in django. 1 public exploit reference exists, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.
Django is subject to SQL injection through its column aliases
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-6w2r-r2m5-xq5w.
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-6w2r-r2m5-xq5w plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
django🐍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 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6. FilteredRelation is subject to SQL injection in column aliases, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed QuerySet.annotate() or QuerySet.alias().
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | all versions | 4.2.24pip install --upgrade 'django==4.2.24' |
| 🐍PyPI | django | ≥ 5.0a1&&< 5.1.12 | 5.1.12pip install --upgrade 'django==5.1.12' |
| 🐍PyPI | django | ≥ 5.2a1&&< 5.2.6 | 5.2.6pip install --upgrade 'django==5.2.6' |
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 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 4.2.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6w2r-r2m5-xq5w 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-6w2r-r2m5-xq5w can be triaged on real exposure rather than presence alone.
Tailored to GHSA-6w2r-r2m5-xq5w. 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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | python3x-django-0:4.2.24-1.el8ap | RHSA-2025:16403 |
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | ansible-automation-platform-24/lightspeed-rhel8:2.4.250225-18 | RHSA-2025:16404 |
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | automation-controller-0:4.6.20-1.el8ap | RHSA-2025:16487 |
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | ansible-automation-platform-25/lightspeed-rhel8:2.5.250924-1 | RHSA-2025:16514 |
| Red Hat OpenStack Platform 16.2 | python-django20-0:2.0.13-20.el8ost | RHSA-2025:17499 |
| Red Hat OpenStack Platform 17.1 for RHEL 9 | python-django-0:2.2.24-12.el9ost | RHSA-2025:17498 |
| Red Hat OpenStack Services on OpenShift 18.0 | python-django-0:3.2.12-9.el9ost | RHSA-2025:17500 |
| Red Hat Satellite 6.15 for RHEL 8 | python-django-0:4.2.24-0.1.el8pc | RHSA-2025:17614 |
Frequently Asked Questions
Is GHSA-6w2r-r2m5-xq5w in your dependencies?
O3 Security finds GHSA-6w2r-r2m5-xq5w across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.