---
id: CVE-2025-13372
aliases:
  - GHSA-rqw2-ghq9-44m7
  - BIT-django-2025-13372
  - PYSEC-2025-104
title: Django is vulnerable to SQL injection in column aliases
summary: Django is vulnerable to SQL injection in column aliases
severity: medium
cvss: 4.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N'
vendor: django
product: django
ecosystem: pip
affected:
  - 'django >= 5.2a1, < 5.2.9'
  - 'django >= 5.1a1, < 5.1.15'
  - 'django >= 4.2a1, < 4.2.27'
patched:
  - django 5.2.9
  - django 5.1.15
  - django 4.2.27
published: '2025-12-02'
updated: '2026-09-10'
sourceUpdated: '2026-09-10T03:50:58.796518425Z'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-rqw2-ghq9-44m7'
references:
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2025-13372'
  - url: >-
      https://github.com/django/django/commit/479415ce5249bcdebeb6570c72df2a87f45a7bbf
  - url: >-
      https://github.com/django/django/commit/56aea00c3c5e1aacf4ed05f8ee06c2e78f02cea0
  - url: >-
      https://github.com/django/django/commit/5b90ca1e7591fa36fccf2d6dad67cf1477e6293e
  - url: >-
      https://github.com/django/django/commit/9c6a5bde24240382807d13bc3748d08444709355
  - url: >-
      https://github.com/django/django/commit/f997037b235f6b5c9e7c4a501491ec45f3400f3d
  - url: 'https://docs.djangoproject.com/en/dev/releases/security'
  - url: 'https://github.com/django/django'
  - url: >-
      https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2025-104.yaml
  - url: 'https://groups.google.com/g/django-announce'
  - url: 'https://www.djangoproject.com/weblog/2025/dec/02/security-releases'
tags:
  - osv
  - pip
epss: 0.00923
epssPercentile: 0.58666
ingestedAt: '2026-09-12T03:13:01.726Z'
---

## Overview

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.

## Affected packages

- `django >= 5.2a1, < 5.2.9`
- `django >= 5.1a1, < 5.1.15`
- `django >= 4.2a1, < 4.2.27`

## Remediation

Upgrade to a patched release:

- `django 5.2.9`
- `django 5.1.15`
- `django 4.2.27`