Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objectsGHSA-frmv-pr5f-9mcr
CRITICALFix: django/django@06dd383GHSA-frmv-pr5f-9mcr is a critical-severity (CVSS 9.1) SQL Injection vulnerability in django. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-frmv-pr5f-9mcr.
EPSS Exploitation Probability
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
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 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8.
The methods QuerySet.filter(), QuerySet.exclude(), and QuerySet.get(), and the class Q(), are subject to SQL injection when using a suitably crafted dictionary, with dictionary expansion, as the _connector argument.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank cyberstan for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | ≥ 5.2a1&&< 5.2.8 | 5.2.8pip install --upgrade 'django==5.2.8' |
| 🐍PyPI | django | ≥ 5.0a1&&< 5.1.14 | 5.1.14pip install --upgrade 'django==5.1.14' |
| 🐍PyPI | django | all versions | 4.2.26pip install --upgrade 'django==4.2.26' |
Affected Products
djangodjangoprojectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Django 5.1.13 - SQL Injection
by Wafcontrol Security Team · Dec 3, 2025
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 5.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-frmv-pr5f-9mcr 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.
The impact of this vulnerability on Red Hat products is limited to the effective user scope of the running process.
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-frmv-pr5f-9mcr (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | ansible-automation-platform-installer-0:2.5-20.el8ap | RHSA-2025:23069 |
| Red Hat Ansible Automation Platform 2.6 for RHEL 9 | automation-controller-0:4.7.6-1.el9ap | RHSA-2025:23070 |
| Red Hat Ansible Automation Platform 2.4 | ansible-automation-platform-24/lightspeed-rhel8:2.4 | RHSA-2025:23130 |
| Red Hat Ansible Automation Platform 2.5 | ansible-automation-platform-25/lightspeed-rhel8:2.5 | RHSA-2025:23131 |
| Red Hat Ansible Automation Platform 2.6 | ansible-automation-platform-26/controller-rhel9:4.7 | RHSA-2025:23133 |
| Red Hat Ansible Automation Platform 2.6 | ansible-automation-platform-tech-preview/ansible-devspaces-rhel9:2.6-1765600296 | RHSA-2025:23196 |
| Red Hat Ansible Automation Platform 2.6 | ansible-automation-platform-26/hub-rhel9:1768873505 | RHSA-2026:1596 |
Frequently Asked Questions
Is GHSA-frmv-pr5f-9mcr in your dependencies?
Find it across PyPI, including transitive dependencies.