CVE-2025-57833Public exploitNetwork attack vector

SQL injection via unchecked FilteredRelation aliases

Published Sep 3, 2025 · Updated Nov 4, 2025

SQL injection in Django 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6 allows remote authenticated users to alter queries. Query.add_filtered_relation() accepted a dictionary-expanded alias without calling the existing alias validator, allowing quotation marks, semicolons, whitespace, and SQL comments into generated SQL. Exploitation requires application code that passes attacker-controlled keys to QuerySet.annotate() or QuerySet.alias(); successful injection can disclose database data or modify it.

CVSS severity7.1
High
EPSS probability15.66%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

SQL injection in Django 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6 allows remote authenticated users to alter queries. Query.add_filtered_relation() accepted a dictionary-expanded alias without calling the existing alias validator, allowing quotation marks, semicolons, whitespace, and SQL comments into generated SQL. Exploitation requires application code that passes attacker-controlled keys to QuerySet.annotate() or QuerySet.alias(); successful injection can disclose database data or modify it.

The record

CVE
CVE-2025-57833
Published
Sep 3, 2025
Updated
Nov 4, 2025
Vendor
Django Software Foundation
Product
Django
Classifications
CWE-89, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 3, 2025CVE publishedPublication date reported by the CVE source.
  2. Nov 4, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.2 <4.2.24
  2. Affected versionversion=5.1 <5.1.12
  3. Affected versionversion=5.2 <5.2.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Django Software Foundation · Djangoversion=4.2 <4.2.24; version=5.1 <5.1.12; version=5.2 <5.2.6

Published CVSS scores

7.1GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo