cve.bz

CVE-2025-13372 djangoproject django: SQL Injection

4.3 mediumEPSS 0.9%Fix available

Medium (4.3) in djangoproject django. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in django 4.2.27, 5.1.15, 5.2.9.

On this page
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.

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 61st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-12-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-13372 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-13372?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-13372?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-13372 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-13372

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-13372](https://cve.bz/cve/badge/CVE-2025-13372.svg)](https://cve.bz/cve/CVE-2025-13372)

HTML:

<a href="https://cve.bz/cve/CVE-2025-13372"><img src="https://cve.bz/cve/badge/CVE-2025-13372.svg" alt="CVE-2025-13372"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
djangoproject Djangofrom 5.2 before 5.2.9
djangoproject Djangofrom 5.1 before 5.1.15
djangoproject Djangofrom 4.2 before 4.2.27

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rqw2-ghq9-44m7PyPIdjango>=5.2a1 <5.2.95.2.9
GHSA-rqw2-ghq9-44m7PyPIdjango>=5.1a1 <5.1.155.1.15
GHSA-rqw2-ghq9-44m7PyPIdjango>=4.2a1 <4.2.274.2.27
PYSEC-2025-104PyPIdjango>=4.2 <4.2.27
>=5.1 <5.1.15
>=5.2 <5.2.9
4.2.27, 5.1.15, 5.2.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12python-django3:3.2.25-0+deb12u1DEBIAN-CVE-2025-13372 DSA-6136-1
Debian13python-django3:4.2.27-0+deb13u1DEBIAN-CVE-2025-13372 DSA-6117-1
Debian14python-django3:4.2.27-1DEBIAN-CVE-2025-13372
Ubuntu22.04:LTSpython-django2:3.2.12-2ubuntu1.24UBUNTU-CVE-2025-13372 USN-7903-1
Ubuntu24.04:LTSpython-django3:4.2.11-1ubuntu1.13UBUNTU-CVE-2025-13372 USN-7903-1
Ubuntu25.10python-django3:5.2.4-1ubuntu2.2UBUNTU-CVE-2025-13372 USN-7903-1
Ubuntu26.04:LTSpython-django3:5.2.9-0ubuntu1UBUNTU-CVE-2025-13372
UbuntuPro:14.04:LTSpython-django1.6.11-0ubuntu1.3+esm9USN-7903-1
UbuntuPro:16.04:LTSpython-django1.8.7-1ubuntu5.15+esm10USN-7903-1
UbuntuPro:18.04:LTSpython-django1:1.11.11-1ubuntu1.21+esm13USN-7903-1
UbuntuPro:20.04:LTSpython-django2:2.2.12-1ubuntu0.29+esm6UBUNTU-CVE-2025-13372 USN-7903-1
SUSELinux Enterprise Module for Package Hub 15 SP6, Linux Enterprise Module for Package Hub 15 SP7python-Django4.2.11-150600.3.44.1SUSE-SU-2025:4384-1
openSUSELeap 15.6python-Django4.2.11-150600.3.44.1SUSE-SU-2025:4384-1
openSUSELeap 16.0python-Django5.2.4-bp160.4.1openSUSE-SU-2025:20153-1
openSUSETumbleweedpython-Django5.2.9-1.1openSUSE-SU-2025:15805-1
openSUSETumbleweedpython-Django44.2.27-1.1openSUSE-SU-2025:15806-1
openSUSETumbleweedpython-Django55.2.16-1.1openSUSE-SU-2026:11270-1
openSUSETumbleweedpython-Django66.0-1.1openSUSE-SU-2026:10005-1
Alpinev3.22, v3.23, v3.24py3-django4.2.27-r0ALPINE-CVE-2025-13372

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated Moderate for Red Hat products. It affects Django applications utilizing PostgreSQL with `FilteredRelation` and specifically crafted dictionaries passed to `QuerySet.annotate()` or `QuerySet.alias()`. Red Hat products shipping affected Django versions that meet these conditions are impacted.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
OpenShift Service Mesh 2openshift-service-mesh/pilot-rhel8Fix deferred
OpenShift Service Mesh 3openshift-service-mesh/istio-cni-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/de-minimal-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/de-minimal-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/de-minimal-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/de-minimal-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/de-minimal-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/lightspeed-rhel9Fix deferred
Red Hat Ansible Automation Platform 2automation-controllerFix deferred
Red Hat Discovery 2discovery/discovery-server-rhel9Fix deferred
Red Hat OpenStack Platform 13 (Queens)rhosp13/openstack-horizonFix deferred
Red Hat OpenStack Platform 16.2rhosp-rhel8/openstack-horizonFix deferred
Red Hat OpenStack Platform 17.1rhosp-rhel9/openstack-horizonFix deferred
Red Hat OpenStack Platform 18.0rhoso/openstack-horizon-rhel9Fix deferred
Red Hat Satellite 6satellite/iop-advisor-backend-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-13372.

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON