LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25986: Django-wiki - Stored Cross-Site Scripting (XSS) in Notifications Section

In Django-wiki, versions 0.0.20 to 0.7.8 are vulnerable to Stored Cross-Site Scripting (XSS) in Notifications Section. An attacker who has access to edit pages can inject JavaScript payload in the title field. When a victim gets a notification regarding the changes made in the application, the payload in the notification panel renders and loads external JavaScript.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw lets someone with page-edit access in Django-wiki store malicious script in a page title. When another user receives a related notification, the notification panel can run that script. Business impact is targeted account or data exposure inside affected wiki deployments, not system takeover.

Executive priority

Treat as a moderate priority for any wiki where many users can edit pages. Patch during the next regular security maintenance window, sooner if editors include external users, contractors, or compromised-account risk is elevated.

Technical view

CVE-2021-25986 is stored XSS in the Django-wiki notifications section, affecting versions 0.0.20 through 0.7.8. The title field is not safely handled in notification rendering, allowing JavaScript execution when a victim views the notification. CVSS 3.1 score is 5.4, CWE-79.

Likely exposure

Exposure is most likely where Django-wiki is deployed and page editing is available to untrusted, semi-trusted, or broad internal users. Risk is lower for private wikis with tightly controlled editor roles and limited notification use.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation requires page-edit privileges and victim interaction with the notification panel. Impact is limited to confidentiality and integrity effects from browser-side script execution.

Researcher notes

Key constraints are low attack complexity, required editor privileges, and required victim interaction. Scope is changed because browser execution can affect another user context. Sources identify the vulnerable feature and version range but do not provide evidence of exploitation in the wild.

Mitigation direction

  • Identify Django-wiki deployments and versions in use.
  • Apply the vendor-published fix or a non-affected release after verification.
  • Restrict page-edit permissions to trusted users until remediated.
  • Review notifications and page titles for unexpected markup or script-like content.
  • Check vendor guidance before relying on temporary workarounds.

Validation and detection

  • Confirm whether any deployment runs Django-wiki 0.0.20 through 0.7.8.
  • Verify who can edit pages and trigger notifications.
  • Review the referenced upstream commit and release notes for the applied fix.
  • Confirm notification rendering escapes page titles after remediation.
  • Retest with benign encoded markup in a non-production environment.
Prepared
Confidence
high
Sources
4

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-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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-25986 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
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2021-25986Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Django-wikiDjango-wiki0.0.20, unspecifiedListed
Weakness

CWE details

CWE-79

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