LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1312: Potential SQL injection via QuerySet.order_by and FilteredRelation

An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. `.QuerySet.order_by()` is subject to SQL injection in column aliases containing periods when the same alias is, using a suitably crafted dictionary, with dictionary expansion, used in `FilteredRelation`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Solomon Kebede for reporting this issue.

HighCVSS 8.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-1312 is a high-severity SQL injection risk in Django. A vulnerable application could allow a logged-in attacker to manipulate database queries through a narrow ORM pattern involving order_by(), FilteredRelation, dictionary expansion, and aliases containing periods. Django fixed supported branches in 6.0.2, 5.2.11, and 4.2.28.

Executive priority

Prioritize remediation for internet-facing or multi-user Django systems, especially where authenticated users can influence filtering or sorting. The exploit conditions are narrow, but successful SQL injection can affect data confidentiality, integrity, and availability.

Technical view

Django QuerySet.order_by() can be SQL injectable when a column alias containing periods is reused through a suitably crafted dictionary expansion in FilteredRelation. The CVSS 3.1 score is 8.5, with network attack vector, high complexity, low privileges required, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely in Django applications running 6.0 before 6.0.2, 5.2 before 5.2.11, or 4.2 before 4.2.28 that use the affected ORM pattern. Unsupported series such as 5.0.x, 4.1.x, and 3.2.x were not evaluated and may also be affected.

Exploitation context

The source bundle does not show KEV listing or confirmed active exploitation. Exploitation appears conditional: the attacker needs low privileges and the application must expose a query path using the specific order_by(), FilteredRelation, alias, and dictionary-expansion pattern.

Researcher notes

Focus review on ORM query construction rather than raw SQL. The key evidence is the vendor-described interaction between QuerySet.order_by(), aliases containing periods, dictionary expansion, and FilteredRelation. Do not assume unsupported Django branches are safe; the source says they were not evaluated.

Mitigation direction

  • Upgrade Django to 6.0.2, 5.2.11, or 4.2.28 as applicable.
  • Move unsupported Django branches to a supported fixed release.
  • Check Red Hat advisories for downstream package availability and status.
  • Review vendor guidance before applying compensating controls not named in sources.

Validation and detection

  • Inventory deployed Django versions across application and container images.
  • Search code for FilteredRelation combined with order_by() and alias dictionaries.
  • Confirm dependency lockfiles and runtime environments use fixed Django versions.
  • Check application dependency scanners for CVE-2026-1312 findings.
  • Review exposed query features requiring authenticated user input.
Prepared
Confidence
high
Sources
11

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.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
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-2026-1312 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
High
CVSS
8.5 (3.1)
Known Exploited
No
Published

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

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.

2CVSS vectors
8Timeline events
2ADP providers
16Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H1.86redhat-SADP
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.5High
CVSS 3.1 vector shape for CVE-2026-1312Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineDSF

    Initial report received.

  2. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  3. Source timelineDSF

    Vulnerability confirmed.

  4. Source timelineDSF

    Security release issued.

  5. ADP timelineredhat-SADP

    Made public.

  6. CVE publishedCVE Program

    The CVE record was published.

  7. ADP timelineredhat-SADP

    Reported to Red Hat.

  8. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPDjango: Django: SQL injection via crafted column aliases in QuerySet.order_by()
other:Red Hat severity ratingcvssV3_1
  • 2026-02-03T15:01:18.274Z: Reported to Red Hat.
  • 2026-02-03T14:36:23.257Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
djangoprojectDjangodjango, 6.0, 6.0.2, 5.2, 5.2.11, 4.2, 4.2.28unaffected
Weakness

CWE details

CWE-89

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs