CVE-2025-57833

Exp

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: 2025-09-03 Last update: 2025-11-04 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-57833 is rated High Exploit Risk (82.1/100): CVSS High severity, with high exploitation likelihood (EPSS 15.60%, 96th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +15.55% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-57833

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-57833

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.05% 15.60% +15.55%
2 2026-05-30 0.02% 0.05% +0.03%
3 2025-11-21 — 0.02% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-57833

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 4.7 [email protected]
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 5.9 [email protected]

Weakness enumeration for CVE-2025-57833

GitHub Security Advisory for CVE-2025-57833

GHSA-6w2r-r2m5-xq5w · Severity: high · Ecosystem: pip — Django is subject to SQL injection through its column aliases

OS Trackers for CVE-2025-57833

vendor priority summary link
alpine high CVE-2025-57833: 1 source package rows (py3-django); 2 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2025-57833
debian not yet assigned CVE-2025-57833 not yet assigned priority: Debian including 1 source packages (python-django), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-57833
redhat high — https://access.redhat.com/security/cve/CVE-2025-57833
suse high CVE-2025-57833 severity important: SUSE including 10 source package names (python3-Django-2.2.28-bp156.18.1, python311-Django-4.2.11-150600.3.30.1, …), 13 product×package rows across 5 product lines (SUSE Linux Enterprise Module for Package Hub 15 SP6, SUSE Linux Enterprise Module for Package Hub 15 SP7, … (5 product lines)): Fixed 13. https://www.suse.com/security/cve/CVE-2025-57833/
ubuntu medium CVE-2025-57833 medium priority: Ubuntu including 1 source packages (python-django), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, trusty, upstream, xenial): released 5, not-affected 3. https://ubuntu.com/security/CVE-2025-57833

Affected software / configurations for CVE-2025-57833

Vendor Product Version Raw CPE
djangoproject django >= 4.2, < 4.2.24 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
djangoproject django >= 5.1, < 5.1.12 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
djangoproject django >= 5.2, < 5.2.6 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*

References for CVE-2025-57833

cvelogic Threat Intelligence