CVE-2020-7471Not scoredCWE-89

CVE-2020-7471: 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.

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

Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL.

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: February 2020
Band: Likely to be exploited (10% or more), February 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-7471 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.