CVE-2025-57833

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 15.6%, top 4% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 16%CVSS: 7.1Exploit: NoneExposed: 0

A fix is available — apply it.

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().

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
48(Track*)
EG Risk 48/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
96.5%
KEV
Not listed

Published

September 3, 2025

Last Modified

November 4, 2025

References (6)

Vendor Advisories for CVE-2025-57833(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-django (3:4.2.18-1ubuntu1.4) @ plucky2026-05-29ubuntu
redhatpython-django-0:4.2.24-0.1.el8pc2025-10-08redhat
redhatpython-django-0:4.2.24-0.1.el9pc2025-10-08redhat
redhatpython-django-0:2.2.24-12.el9ost2025-10-07redhat
redhatpython-django20-0:2.0.13-20.el8ost2025-10-07redhat
redhatpython-django-0:3.2.12-9.el9ost2025-10-07redhat
redhatansible-automation-platform-25/lightspeed-rhel8:2.5.250924-12025-09-23redhat
redhatpython3.11-django-0:4.2.24-1.el9ap2025-09-23redhat
redhatpython-django-0:4.2.24-1.el9ap2025-09-22redhat
redhatansible-automation-platform-24/lightspeed-rhel8:2.4.250225-182025-09-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
django4.2 ... 5.2.5 (42 versions)5.2.6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(11)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:59 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:02 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 01:59 UTCEPSS rescore
  13. 2026-07-15 01:59 UTCEPSS rescore
  14. 2026-07-13 22:29 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-09 19:09 UTCEPSS rescore
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-07 13:45 UTCEPSS rescore
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 04:32 UTCOSV refresh
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-06 02:23 UTCEPSS rescore
Show 58 more
  1. 2026-07-05 02:30 UTCEPSS rescore
  2. 2026-07-04 06:30 UTCEPSS rescore
  3. 2026-07-02 17:01 UTCEPSS rescore
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-28 14:07 UTCEPSS rescore
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 04:55 UTCEPSS rescore
  11. 2026-06-27 03:08 UTCEPSS rescore
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-24 14:04 UTCEPSS rescore
  15. 2026-06-24 14:04 UTCEPSS rescore
  16. 2026-06-23 21:32 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-21 01:59 UTCEPSS rescore
  20. 2026-06-19 19:25 UTCEPSS rescore
  21. 2026-06-19 19:25 UTCEPSS rescore
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-17 17:52 UTCEPSS rescore
  25. 2026-06-17 15:43 UTCOSV refresh
  26. 2026-06-16 17:52 UTCEPSS rescore
  27. 2026-06-16 17:52 UTCEPSS rescore
  28. 2026-06-15 17:48 UTCEPSS rescore
  29. 2026-06-14 23:17 UTCEPSS rescore
  30. 2026-06-13 23:00 UTCEPSS rescore
  31. 2026-06-12 23:11 UTCEPSS rescore
  32. 2026-06-11 14:00 UTCEPSS rescore
  33. 2026-06-11 14:00 UTCEPSS rescore
  34. 2026-06-10 22:18 UTCEPSS rescore
  35. 2026-06-10 22:18 UTCEPSS rescore
  36. 2026-06-10 13:22 UTCEPSS rescore
  37. 2026-06-10 13:22 UTCEPSS rescore
  38. 2026-06-08 14:16 UTCEPSS rescore
  39. 2026-06-08 14:16 UTCEPSS rescore
  40. 2026-06-07 15:24 UTCEPSS rescore
  41. 2026-06-07 15:24 UTCEPSS rescore
  42. 2026-06-06 13:47 UTCEPSS rescore
  43. 2026-06-06 13:47 UTCEPSS rescore
  44. 2026-06-05 22:46 UTCEPSS rescore
  45. 2026-06-05 22:46 UTCEPSS rescore
  46. 2026-06-05 06:10 UTCEPSS rescore
  47. 2026-06-05 06:10 UTCEPSS rescore
  48. 2026-06-04 13:12 UTCEPSS rescore
  49. 2026-06-04 13:12 UTCEPSS rescore
  50. 2026-06-01 13:51 UTCEPSS rescore
  51. 2026-06-01 13:51 UTCEPSS rescore
  52. 2026-05-31 22:30 UTCEPSS rescore
  53. 2026-05-31 22:30 UTCEPSS rescore
  54. 2026-05-31 00:16 UTCEPSS rescore
  55. 2026-05-31 00:16 UTCEPSS rescore
  56. 2026-05-29 13:44 UTCEPSS rescore
  57. 2026-05-29 13:33 UTCEG score recompute
  58. 2026-05-29 13:33 UTCVendor advisory

Publicly available exploits

(3 references)

Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCsw0rd1ight/CVE-2025-57833
    First seen Nov 2, 2025

    Analysis and reproduction of CVE-2025-57833

    Open source ↗
  • GitHub PoCloic-houchi/Django-faille-CVE-2025-57833_test
    First seen Sep 9, 2025
    Open source ↗
  • GitHub PoCMkway/CVE-2025-57833
    First seen Sep 5, 2025

    We've set up an environment to test CVE-2025-57833. This environment was built using AI, so it's subject to ongoing modification.

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-57833?
CVE-2025-57833 is a high vulnerability published on September 3, 2025. 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().
When was CVE-2025-57833 disclosed?
CVE-2025-57833 was first published in the National Vulnerability Database on September 3, 2025, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-57833 actively exploited?
CVE-2025-57833 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-57833?
CVE-2025-57833 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2025-57833?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-57833, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-57833

Explore →

Is Your Infrastructure Affected by CVE-2025-57833?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs