CVE-2019-14234Not scoredCWE-89

CVE-2019-14234: 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.

47.7%probability of exploitation in the next 30 days

98th percentile

050100

Higher than 98% of scored CVEs

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

DescriptionCVE.org

An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. Due to an error in shallow key transformation, key and index lookups for django.contrib.postgres.fields.JSONField, and key lookups for django.contrib.postgres.fields.HStoreField, were subject to SQL injection. This could, for example, be exploited via crafted use of "OR 1=1" in a key or index name to return all records, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to the QuerySet.filter() function.

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

CoverageNo articles yet

No CyberSIXT article names CVE-2019-14234 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.