CVE-2024-11319: Stored XSS in Open Source Project "django-cms"
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in django CMS Association django-cms allows Cross-Site Scripting (XSS).
This issue affects django-cms: 3.11.7, 3.11.8, 4.1.2, 4.1.3.
Security readout for executives and security teams
Plain-English summary
CVE-2024-11319 is a stored cross-site scripting issue in django CMS. A highly privileged CMS user could save unsafe content that later affects another user who views the generated page or CMS output. Business impact is mainly editor or administrator session risk and possible content integrity issues, not direct server takeover.
Executive priority
Treat this as a moderate-priority web application issue. It should be remediated in normal patch cycles, faster for sites with many editors, external content contributors, or sensitive administrator sessions.
Technical view
The CVE describes CWE-79 improper input neutralization in django-cms, with CVSS 4.8. The vector is network reachable, low complexity, high privileges required, user interaction required, changed scope, and low confidentiality and integrity impact. The source bundle names django-cms 3.11.7, 3.11.8, 4.1.2, 4.1.3, and also lists 4.1.4 in affected data.
Likely exposure
Exposure is most likely on public or internal sites running the listed django CMS versions, especially where multiple staff or third parties can edit CMS pages. Risk is lower where CMS access is tightly restricted and privileged accounts are well protected.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not support active exploitation. A public researcher source describes stored XSS involving the page title field, but the CVSS vector indicates exploitation requires high privileges and a victim interaction step.
Researcher notes
Evidence is consistent with stored XSS, but the bundle has a version ambiguity because 4.1.4 appears in affected data while the prose lists 4.1.2 and 4.1.3. Validate fixed and affected ranges directly against the django CMS advisory and commit history.
Mitigation direction
Inventory django CMS deployments and record exact installed versions.
Review the django CMS security update and linked fix commit.
Apply the vendor-supported security update after confirming fixed versions.
Restrict CMS administrator and editor access to trusted accounts.
Review recent page title and content changes for suspicious entries.
Monitor privileged CMS sessions for unusual activity.
Validation and detection
Check dependency manifests or runtime package metadata for django-cms versions.
Confirm whether any deployment matches the affected versions in the CVE data.
Review CMS roles and identify users with page editing privileges.
Inspect recent CMS page title changes for unexpected script-like content.
Verify remediation against the vendor advisory, not assumptions from version numbers.
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-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.