Security readout for executives and security teams
Plain-English summary
This Django flaw could let an unauthenticated remote attacker make certain template sorting logic reveal sensitive information or trigger an unintended method call. The issue is limited to affected Django versions and requires exposure through the dictsort template filter with a crafted key.
Executive priority
Prioritize remediation for internet-facing Django applications, especially where templates process user-controlled sorting inputs. Treat this as a high-priority patching issue, but not as confirmed active exploitation based on the provided evidence.
Technical view
CVE-2021-45116 affects Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. The dictsort template filter reused Django Template Language variable resolution logic, creating potential information disclosure or unintended method invocation when processing a crafted key.
Likely exposure
Likely exposure is Django web applications on the affected versions that use the dictsort template filter where a key can be influenced by untrusted input. The source bundle does not identify specific affected downstream products beyond advisory references.
Exploitation context
The CVE has a high CVSS score of 7.5 with network, low-complexity, unauthenticated characteristics. However, KEV is false, and the provided sources do not state that this vulnerability is actively exploited in the wild.
Researcher notes
The affected component is Django Template Language handling inside dictsort. Validation should focus on version confirmation and template data-flow review, not exploit reproduction. The affected product metadata in the source bundle is incomplete, so environment inventory is essential.
Mitigation direction
- Upgrade Django 2.2 deployments to 2.2.26 or later.
- Upgrade Django 3.2 deployments to 3.2.11 or later.
- Upgrade Django 4.0 deployments to 4.0.1 or later.
- Check Django, Fedora, and downstream vendor guidance for package-specific remediation.
- Review dictsort usage where sort keys may be influenced by users.
Validation and detection
- Inventory applications and packages using Django 2.2, 3.2, or 4.0.
- Confirm deployed Django versions meet the fixed release thresholds.
- Search templates for dictsort filter usage.
- Assess whether dictsort keys can be influenced by untrusted input.
- Verify OS or vendor packages include the relevant security update.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2021-45116 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://groups.google.com/forum/#%21forum/django-announceCVE reference · x_refsource_MISC
- https://docs.djangoproject.com/en/4.0/releases/security/CVE reference · x_refsource_MISC
- https://www.djangoproject.com/weblog/2022/jan/04/security-releases/CVE reference · x_refsource_CONFIRM
- https://security.netapp.com/advisory/ntap-20220121-0005/CVE reference · x_refsource_CONFIRM
- FEDORA-2022-e7fd530688CVE reference · vendor-advisory, x_refsource_FEDORA
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.