PYSEC-2025-104

Vulnerability from pysec - Published: 2025-12-02 16:15 - Updated: 2026-05-20 09:18
VLAI?
Details

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 ?
4.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Impacted products
Name purl
django pkg:pypi/django
Aliases
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "django",
        "purl": "pkg:pypi/django"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "4.2"
            },
            {
              "fixed": "4.2.27"
            },
            {
              "introduced": "5.1"
            },
            {
              "fixed": "5.1.15"
            },
            {
              "introduced": "5.2"
            },
            {
              "fixed": "5.2.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.2",
        "4.2.1",
        "4.2.10",
        "4.2.11",
        "4.2.12",
        "4.2.13",
        "4.2.14",
        "4.2.15",
        "4.2.16",
        "4.2.17",
        "4.2.18",
        "4.2.19",
        "4.2.2",
        "4.2.20",
        "4.2.21",
        "4.2.22",
        "4.2.23",
        "4.2.24",
        "4.2.25",
        "4.2.26",
        "4.2.3",
        "4.2.4",
        "4.2.5",
        "4.2.6",
        "4.2.7",
        "4.2.8",
        "4.2.9",
        "5.1",
        "5.1.1",
        "5.1.10",
        "5.1.11",
        "5.1.12",
        "5.1.13",
        "5.1.14",
        "5.1.2",
        "5.1.3",
        "5.1.4",
        "5.1.5",
        "5.1.6",
        "5.1.7",
        "5.1.8",
        "5.1.9",
        "5.2",
        "5.2.1",
        "5.2.2",
        "5.2.3",
        "5.2.4",
        "5.2.5",
        "5.2.6",
        "5.2.7",
        "5.2.8"
      ]
    }
  ],
  "aliases": [
    "CVE-2025-13372"
  ],
  "details": "An issue was discovered in 5.2 before 5.2.9, 5.1 before 5.1.15, and 4.2 before 4.2.27.\n`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.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.\nDjango would like to thank Stackered for reporting this issue.",
  "id": "PYSEC-2025-104",
  "modified": "2026-05-20T09:18:57.284097Z",
  "published": "2025-12-02T16:15:53.907Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://groups.google.com/g/django-announce"
    },
    {
      "type": "FIX",
      "url": "https://docs.djangoproject.com/en/dev/releases/security/"
    },
    {
      "type": "FIX",
      "url": "https://www.djangoproject.com/weblog/2025/dec/02/security-releases/"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.