CVE-2022-34265 - CVE House
Back to Database
Status published Critical CVE-2022-34265

An issue was discovered in Django 3.2 before 3.2.14 and...

Vulnerability Description

An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2022-34265

Credits & Attribution

No credits recorded in the NVD database.

References

More from djangoproject

View All →
CVE-2025-64460
Potential denial-of-service vulnerability in XML serializer text extraction
Unknown 0
CVE-2025-64459
Potential SQL injection via _connector keyword argument in QuerySet and Q objects
Unknown 0
CVE-2025-64458
Potential denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
Unknown 0
CVE-2025-59682
An issue was discovered in Django 4.2 before 4.2.25, 5.1...
Low 3.1
CVE-2025-59681
An issue was discovered in Django 4.2 before 4.2.25, 5.1...
High 7.1

Affected Vendor

djangoproject

View all reports →

Affected Software

django
Vulnerable Versions:
3.2, 4.0

Timeline

Official Publish: July 4th, 2022
Last Modified: February 13th, 2025
Added to House: July 21st, 2026

CVSS Vectors

V3: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.