Skip to content
vulneraibility.com
Screener

CVE-2025-64459

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.

CVSS
9.1Criticalscored by CISA
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
19.3%chance of exploitation in the next 30 daystop 3% of scored CVEsFIRST score of 11 Nov 2026
Fix
Fixed in 5.2.8, 5.1.14, 4.2.26per the vendor
Published
5 Nov 2025analysed here 12 Nov 2026

Do first. Upgrade to a fixed release: 5.2.8, 5.1.14, 4.2.26.

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Yes. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
djangoproject Django>= 5.2 and < 5.2.8>= 5.1 and < 5.1.14>= 4.2 and < 4.2.26Vendor says fixed in: 5.2.8, 5.1.14, 4.2.26

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • djangoproject:django

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Yes. SQL injection puts SQL syntax into a request parameter, and WAF signatures recognise that syntax well. Cloudflare also publishes a rule written for this CVE.

Also consider: parameterized queries · ORM

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Yes: 1 on Exploit-DB · 10 GitHub proofs of concept
CISA SSVC
exploitation none, automatable yes, technical impact totalAssessed by CISA 6 Nov 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Exploit-DB

GitHub proofs of concept

and 6 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 5 Nov 2025Published
  2. 6 Nov 2025First public exploit or proof of conceptsame day later
  3. 6 Nov 2025CISA SSVC assessment: exploitation nonesame day later
  4. 26 Feb 2026CVE record last updated113 days (about 4 months) later
  5. 12 Nov 2026Analysed by vulneraibility.com259 days (about 9 months) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityNoneThe service stays up.

Common questions

Is CVE-2025-64459 being exploited?

Not confirmed. CVE-2025-64459 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 19% probability of exploitation in the next 30 days.

How severe is CVE-2025-64459?

CVE-2025-64459 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-64459?

Yes. A fix has been recorded for CVE-2025-64459. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-64459 affect?

CVE-2025-64459 affects djangoproject:django. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

4 references in the CVE record, grouped by the tags the record gives them.

Advisories (2)

Other links (2)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com