Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2025-57833: 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.

HighCVSS 8.1 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Plan (action score 40/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 28.2% (FIRST EPSS); higher than 98.1% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: py3-django (Alpine:v3.22) 4.2.24-r0; python-django (Debian:11) 2:2.2.28-1~deb11u8; python-django (Debian:12) 3:3.2.25-0+deb12u1.

Add it to your regular patch cycle. Upgrade to py3-django (Alpine:v3.22) 4.2.24-r0; python-django (Debian:11) 2:2.2.28-1~deb11u8; python-django (Debian:12) 3:3.2.25-0+deb12u1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

Published
Sep 3, 2025
Updated
Jun 17, 2026
EPSS
28.2% · 98th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
8 / 30 · 28.2%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.1
CNA · mitre
7.1
1.0 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-57833

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
djangoprojectdjango

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

  • djangoproject Django

    • 4.2 and later · before 4.2.24affected
    • 5.1 and later · before 5.1.12affected
    • 5.2 and later · before 5.2.6affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • djangoproject django4.2 and later · before 4.2.24
  • djangoproject django5.1 and later · before 5.1.12
  • djangoproject django5.2 and later · before 5.2.6

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.22py3-djangobefore 4.2.24-r04.2.24-r0
Debian:11python-djangobefore 2:2.2.28-1~deb11u82:2.2.28-1~deb11u8
Debian:12python-djangobefore 3:3.2.25-0+deb12u13:3.2.25-0+deb12u1
Debian:13python-djangobefore 3:4.2.27-0+deb13u13:4.2.27-0+deb13u1
Debian:14python-djangobefore 3:4.2.24-13:4.2.24-1
openSUSE:Leap 15.6python-Djangobefore 4.2.11-150600.3.30.14.2.11-150600.3.30.1
openSUSE:Tumbleweedpython-Djangobefore 5.2.6-1.15.2.6-1.1
openSUSE:Tumbleweedpython-Django4before 4.2.24-1.14.2.24-1.1
PyPIdjangofrom 4.2 · before 4.2.244.2.24
PyPIdjangofrom 5.0a1 · before 5.1.125.1.12
PyPIdjangofrom 5.1 · before 5.1.125.1.12
PyPIdjangofrom 5.2 · before 5.2.65.2.6
PyPIdjangofrom 5.2a1 · before 5.2.65.2.6
PyPIdjangobefore 4.2.244.2.24
Red Hat:ansible_automation_platform_developer:2.5::el8python3.11-djangobefore 0:4.2.24-1.el8ap0:4.2.24-1.el8ap
Red Hat:ansible_automation_platform_developer:2.5::el9python3.11-djangobefore 0:4.2.24-1.el9ap0:4.2.24-1.el9ap
Red Hat:ansible_automation_platform:2.4::el8python39-djangobefore 0:4.2.24-1.el8ap0:4.2.24-1.el8ap
Red Hat:ansible_automation_platform:2.4::el8python3x-djangobefore 0:4.2.24-1.el8ap0:4.2.24-1.el8ap
Red Hat:ansible_automation_platform:2.4::el9python-djangobefore 0:4.2.24-1.el9ap0:4.2.24-1.el9ap
Red Hat:ansible_automation_platform:2.4::el9python3-djangobefore 0:4.2.24-1.el9ap0:4.2.24-1.el9ap
Red Hat:ansible_automation_platform:2.5::el8automation-controller-venv-towerbefore 0:4.6.20-1.el8ap0:4.6.20-1.el8ap
Red Hat:ansible_automation_platform:2.5::el9automation-controller-venv-towerbefore 0:4.6.20-1.el9ap0:4.6.20-1.el9ap
Red Hat:openstack:16.2::el8python-django20before 0:2.0.13-20.el8ost0:2.0.13-20.el8ost
Red Hat:openstack:16.2::el8python3-django20before 0:2.0.13-20.el8ost0:2.0.13-20.el8ost

+18

Other highest-scoring records for the same primary product.

  • CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
    61This week
  • CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter…
    59Plan
  • CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.
    55Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-32873May 8, 2025 · An issue was discovered in Django 4.2 before 4.2.21, 5.1 before 5.1.9, and 5.2 before 5.2.1.
    25Monitor
  • ← EarlierCVE-2025-48432Jun 4, 2025 · An issue was discovered in Django 5.2 before 5.2.3, 5.1 before 5.1.11, and 4.2 before 4.2.23.
    21Monitor
  • Later →CVE-2025-59681Oct 1, 2025 · An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7.
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:py3-django4.2.24-r0 · Alpine:v3.22Package registry (OSV)
debian:python-django3:3.2.25-0+deb12u1 · Debian:12Package registry (OSV)
opensuse:python-Django4.2.11-150600.3.30.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python-Django44.2.24-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:django4.2.24Package registry (OSV)
PyPI:django5.1.12Package registry (OSV)
PyPI:django5.2.6Package registry (OSV)
red hat:automation-controller-venv-tower0:4.6.20-1.el8ap · Red Hat:ansible_automation_platform:2.5::el8Package registry (OSV)
red hat:cjson0:1.7.18-2.el9sat · Red Hat:satellite_capsule:6.17::el9Package registry (OSV)
red hat:cjson-debuginfo0:1.7.18-2.el9sat · Red Hat:satellite_capsule:6.17::el9Package registry (OSV)
red hat:cjson-debugsource0:1.7.18-2.el9sat · Red Hat:satellite_capsule:6.17::el9Package registry (OSV)
red hat:puppet-agent0:8.8.1-3.el9sat · Red Hat:satellite_capsule:6.17::el9Package registry (OSV)
red hat:python-django0:4.2.24-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9Package registry (OSV)
red hat:python-django200:2.0.13-20.el8ost · Red Hat:openstack:16.2::el8Package registry (OSV)
red hat:python3-django0:4.2.24-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9Package registry (OSV)
red hat:python3-django200:2.0.13-20.el8ost · Red Hat:openstack:16.2::el8Package registry (OSV)
red hat:python3.11-django0:4.2.24-1.el8ap · Red Hat:ansible_automation_platform_developer:2.5::el8Package registry (OSV)
red hat:python39-django0:4.2.24-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8Package registry (OSV)
red hat:python3x-django0:4.2.24-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8Package registry (OSV)
suse:python-Django4.2.11-150600.3.30.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×5

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHub5 repositories2025-09-05 → 2025-11-27

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+1 d
  3. TodayNov 16, 2026+439 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-6445963 days apartPotential SQL injection via _connector keyword argument in QuerySet and Q objects
    42Plan
  • CVE-2025-5968128 days apartAn issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7.
    39Monitor
  • CVE-2024-53908271 days apartAn issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17.
    39Monitor
  • CVE-2024-42005392 days apartAn issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15.
    29Monitor
  • CVE-2026-1207153 days apartPotential SQL injection via raster lookups on PostGIS
    25Monitor
  • CVE-2026-1312153 days apartPotential SQL injection via QuerySet.order_by and FilteredRelation
    21Monitor

Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = '" + owner + "'");

Fixed

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = $1",  [owner]);

References

All records