Skip to content
Connect AISign inSign up free
CVE-2025-596817.1HighCWE-89

CVE-2025-59681: djangoproject vulnerability

djangoproject · Django

Vendor fix available · Affected: djangoproject · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.7%probability of exploitation in the next 30 days
52nd percentile
050100

Higher than 52% of scored CVEs

7.1HighCVSS 3.1
LowHigh

DescriptionCVE.org

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).

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • djangoproject · Djangofrom 4.2 before 4.2.25; from 5.1 before 5.1.13; from 5.2 before 5.2.7

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
October 2025

Disclosed bug bounty reports about CVE-2025-59681

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

CoverageNo articles yet

No CyberSIXT article names CVE-2025-59681 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References