CVE-2022-34265Not scoredCWE-89

CVE-2022-34265: Djangoproject vulnerability

Djangoproject · Django

Vendor fix available · Affected: Djangoproject · Exploitation: likely to be exploited (10% or more)

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

73.6%probability of exploitation in the next 30 days

99th percentile

050100

Higher than 99% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

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

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: SQL Injection
Vendor: Djangoproject
Published: July 2022
Band: Likely to be exploited (10% or more), July 2022

CoverageNo articles yet

No CyberSIXT article names CVE-2022-34265 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.