CVE-2025-57833

Djangoproject Django SQL injection

7.1 HIGHPublic exploitEPSS 17.4%

Published3 Sept 2025

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

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityHigh

Privileges requiredLow

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityLow

AvailabilityNone

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

Affected products

Djangoproject Django≥ 4.2 < 4.2.24 · ≥ 5.1 < 5.1.12 · ≥ 5.2 < 5.2.6

Remediation

Fixed in

Djangoproject Django≥ 4.2.24

Patch & vendor advisories

References

https://docs.djangoproject.com/en/dev/releases/security/Vendor Advisory
https://groups.google.com/g/django-announceVendor Advisory
https://lists.debian.org/debian-lts-announce/2025/09/msg00017.html
https://medium.com/@EyalSec/django-unauthenticated-0-click-rce-and-sql-injection-using-default-configuration-059964f3f898ExploitThird Party Advisory
https://www.djangoproject.com/weblog/2025/sep/03/security-releases/Vendor Advisory
http://www.openwall.com/lists/oss-security/2025/09/03/3

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-57833 being actively exploited?

CVE-2025-57833 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 17.4%.

How severe is CVE-2025-57833?

CVE-2025-57833 has a CVSS 3.1 base score of 7.1, rated high. EPSS estimates a 17.4% probability of exploitation.

Which products are affected by CVE-2025-57833?

Affected products include Djangoproject Django.

How do I fix CVE-2025-57833?

Upgrade affected software to a fixed version, for example Djangoproject Django 4.2.24 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-57833 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.