SQL Injection Affecting python311-Django package, versions <4.2.11-150600.3.33.1


Severity

Recommended
0.0
critical
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.01% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about SQL Injection vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-SLES157-PYTHON311DJANGO-13283750
  • published4 Oct 2025
  • disclosed2 Oct 2025

Introduced: 2 Oct 2025

NewCVE-2025-59681  (opens in a new tab)
CWE-89  (opens in a new tab)

How to fix?

Upgrade SLES:15.7 python311-Django to version 4.2.11-150600.3.33.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python311-Django package and not the python311-Django package as distributed by SLES. See How to fix? for SLES:15.7 relevant fixed versions and status.

An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7. QuerySet.annotate(), QuerySet.alias(), QuerySet.aggregate(), and QuerySet.extra() are subject to SQL injection in column aliases, when using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to these methods (on MySQL and MariaDB).

CVSS Base Scores

version 3.1