LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35042: Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is unt...

Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Django SQL injection flaw in specific 3.1 and 3.2 releases. Risk depends on whether an application lets users influence database sorting passed into QuerySet.order_by. Public-facing apps with affected versions and user-controlled sort parameters deserve prompt review and upgrade.

Executive priority

Treat as a near-term remediation item for Django-backed public services, especially where users can sort records. It is not marked as known exploited in the bundle, but SQL injection can create serious data confidentiality and integrity risk.

Technical view

CVE-2021-35042 affects Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5. The source bundle describes SQL injection through QuerySet.order_by when untrusted client input is used. Exposure is application-dependent because vulnerable framework versions alone are not enough without unsafe data flow.

Likely exposure

Likely exposure is Django web applications on affected 3.1.x or 3.2.x releases that pass request-controlled ordering values into QuerySet.order_by. Apps using fixed server-side ordering or patched Django versions have lower apparent exposure.

Exploitation context

The bundle does not show KEV listing or cited evidence of active exploitation. Practical abuse requires an application route where an attacker can control order_by input. No exploit steps or public weaponization evidence are included in the provided sources.

Researcher notes

Focus analysis on data flow from HTTP request parameters into QuerySet.order_by. The evidence names affected Django release ranges and fixed versions, but does not provide CVSS, CWE, exploit status, or complete downstream product impact.

Mitigation direction

  • Upgrade Django 3.1.x to 3.1.13 or later.
  • Upgrade Django 3.2.x to 3.2.5 or later.
  • Avoid passing raw client input to QuerySet.order_by.
  • Allowlist supported sort fields and directions server-side.
  • Check vendor advisories for packaged products embedding Django.
  • Prioritize internet-facing routes with user-controlled sorting.

Validation and detection

  • Inventory deployed Django versions across applications and containers.
  • Review request handlers for QuerySet.order_by using client parameters.
  • Confirm public routes expose sorting or ordering controls.
  • Verify patched versions are deployed in production.
  • Review vendor advisories for downstream product exposure.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-35042 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.