CVE-2025-57833: Django: Potential SQL injection in Filtedlation column aliases

Published Sep 3, 2025
·
Updated

An issue was discovered in Django 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6. FilteredRelation is subject to SQL injection in column aliases, using a suitably crafted dictionary, with dictionary expansion, as the kwargs passed QuerySet.annotate() or QuerySet.alias().

Affected Software

11 affected componentsFixes available
Django Software Foundation Django<4.2.24, <5.1.12, <5.2.6
pip/django>=5.2a1<5.2.6
5.2.6
pip/django>=5.0a1<5.1.12
5.1.12
pip/django<4.2.24
4.2.24
djangoproject Django>=4.2<4.2.24
djangoproject Django>=5.1<5.1.12
djangoproject Django>=5.2<5.2.6
alpine/py3-django<4.2.24-r0
4.2.24-r0
alpine/py3-django<4.2.24-r0
4.2.24-r0
alpine/py3-django<4.2.24-r0
4.2.24-r0
debian/python-django
3:3.2.25-0+deb12u33:3.2.25-0+deb12u63:4.2.28-0+deb13u23:4.2.28-0+deb13u13:5.2.19-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 5.2.6
  2. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 5.1.12
  3. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 4.2.24
  4. Upgrade

    Upgrade alpine/py3-django to a version that resolves this vulnerability.

    Fixed in 4.2.24-r0
  5. Upgrade

    Upgrade debian/python-django to a version that resolves this vulnerability.

    Fixed in 3:3.2.25-0+deb12u3Fixed in 3:3.2.25-0+deb12u6Fixed in 3:4.2.28-0+deb13u2Fixed in 3:4.2.28-0+deb13u1Fixed in 3:5.2.19-1

Event History

Sep 3, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·09:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·09:15 PM
DescriptionSeverityAffected Software
Sep 5, 2025
Exploit Published
via GitHub·05:03 AM
Sep 8, 2025
Advisory Published
via GitHub·06:31 PM
Data Sourced
via GitHub·06:31 PM
DescriptionSeverityWeaknessAffected Software
Nov 4, 2025
Data Sourced
via NVD·10:16 PM
Affected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2025-57833?

CVE-2025-57833 is considered a critical vulnerability due to its potential for SQL injection.

2

How do I fix CVE-2025-57833?

To fix CVE-2025-57833, upgrade to Django version 4.2.24, 5.1.12, or 5.2.6 or later.

3

What are the affected versions for CVE-2025-57833?

CVE-2025-57833 affects Django versions prior to 4.2.24, 5.1.12, and 5.2.6.

4

What functionality is impacted by CVE-2025-57833?

CVE-2025-57833 impacts the filteredRelation feature in Django, allowing for potential SQL injection via column aliases.

5

Is CVE-2025-57833 specific to certain implementations of Django?

Yes, CVE-2025-57833 is specifically applicable to Django implementations utilizing the QuerySet.annotate() or QuerySet.alias() methods.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203