NVD / CVE Program· CNA DSF

CVE-2025-13372: Potential SQL injection in FilteredRelation column aliases on PostgreSQL

Noroxi assessment

Priority: Monitor (action score 17/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.92% (FIRST EPSS); higher than 60.2% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
Fixed version: djangoproject Django 4.2.27, 5.1.15, 5.2.9.

Low priority for now. Upgrade to djangoproject Django 4.2.27, 5.1.15, 5.2.9 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 5.2 before 5.2.9, 5.1 before 5.1.15, and 4.2 before 4.2.27. `FilteredRelation` is subject to SQL injection in column aliases, using a suitably crafted dictionary, with dictionary expansion, as the `**kwargs` passed to `QuerySet.annotate()` or `QuerySet.alias()` on PostgreSQL. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Stackered for reporting this issue.

MediumCVSS 4.3 · v3.1—No exploit Fix available

Published: Dec 2, 2025
Updated: Oct 18, 2026
EPSS: 0.9% · 60th percentile
CWE: CWE-89

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 17 / 40 · 4.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.9%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

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

Running WordPress? Scan your site free with WP Lens

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.

Vendor	Product	CPE
djangoproject	django	cpe:2.3:a:djangoproject:django

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.27
djangoproject django5.1 and later · before 5.1.15
djangoproject django5.2 and later · before 5.2.9

Versions reported by the vendor

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

djangoproject Django
- 5.2.9, 5.1.15, 4.2.27not affected
- 5.2 and later · before 5.2.9affected · semver
- 5.1 and later · before 5.1.15affected · semver
- 4.2 and later · before 4.2.27affected · semver

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:12	python-django	before 3:3.2.25-0+deb12u1	3:3.2.25-0+deb12u1
Debian:13	python-django	before 3:4.2.27-0+deb13u1	3:4.2.27-0+deb13u1
Debian:14	python-django	before 3:4.2.27-1	3:4.2.27-1
openSUSE:Leap 15.6	python-Django	before 4.2.11-150600.3.44.1	4.2.11-150600.3.44.1
openSUSE:Leap 16.0	python-Django	before 5.2.4-bp160.4.1	5.2.4-bp160.4.1
openSUSE:Tumbleweed	python-Django	before 5.2.9-1.1	5.2.9-1.1
openSUSE:Tumbleweed	python-Django4	before 4.2.27-1.1	4.2.27-1.1
PyPI	django	from 4.2 · before 4.2.27	4.2.27
PyPI	django	from 4.2a1 · before 4.2.27	4.2.27
PyPI	django	from 5.1 · before 5.1.15	5.1.15
PyPI	django	from 5.1a1 · before 5.1.15	5.1.15
PyPI	django	from 5.2 · before 5.2.9	5.2.9
PyPI	django	from 5.2a1 · before 5.2.9	5.2.9
SUSE:Linux Enterprise Module for Package Hub 15 SP6	python-Django	before 4.2.11-150600.3.44.1	4.2.11-150600.3.44.1

Same product

djangoproject: all records

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-64458Nov 5, 2025 · Potential denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
31Monitor
← EarlierCVE-2025-64459Nov 5, 2025 · Potential SQL injection via _connector keyword argument in QuerySet and Q objects
42Plan
Later →CVE-2025-64460Dec 2, 2025 · Potential denial-of-service vulnerability in XML serializer text extraction
31Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
djangoproject Django	4.2.27	Vendor (CNA)
djangoproject Django	5.1.15	Vendor (CNA)
djangoproject Django	5.2.9	Vendor (CNA)
debian:python-django	3:3.2.25-0+deb12u1 · Debian:12	Package registry (OSV)
opensuse:python-Django	4.2.11-150600.3.44.1 · openSUSE:Leap 15.6	Package registry (OSV)
opensuse:python-Django4	4.2.27-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
PyPI:django	4.2.27	Package registry (OSV)
PyPI:django	5.1.15	Package registry (OSV)
PyPI:django	5.2.9	Package registry (OSV)
suse:python-Django	4.2.11-150600.3.44.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Stackeredreporter
Jacob Wallsremediation developer
Natalia Bidartcoordinator

Variant candidates

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

CVE-2025-6445927 days apartPotential SQL injection via _connector keyword argument in QuerySet and Q objects
42Plan
CVE-2025-5783390 days apartAn issue was discovered in Django 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6.
40Plan
CVE-2025-5968162 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-53908361 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-42005482 days apartAn issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15.
29Monitor
CVE-2026-120763 days apartPotential SQL injection via raster lookups on PostGIS
25Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
A user must open a link or visit a page.
No special conditions are required; it is repeatable.

If successful

Confidentiality: low · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVSS vector

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

nvd-secondary

Root cause

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

The bug in code

The whole CWE-89 class

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

Vulnerable

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

Fixed

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

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

docs.djangoproject.com/en/dev/releases/security/

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records