Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain wiki account / trigger Thanks action
-
DeliveryStore crafted script in vulnerable field
-
ExploitVictim views notification or page
-
ExecutionScript executes in victim browser (S:C)
-
ImpactSteal session token or act as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the MediaWiki Thanks extension to be installed and enabled (it is bundled with MediaWiki but optional), an attacker able to store a malicious payload through a Thanks-related action or field, and - critically - a victim user who subsequently views the page/notification that renders the unescaped value (UI:R). The scope change (S:C) means the payload executes in the victim's browser rather than compromising the server directly. Limiting factors: the need for victim interaction, likely a wiki account to perform the storing action (the CVSS PR:N is questionable given the extension's workflow), and impact confined to browser-context script execution (C:L/I:L, no availability impact). Affected: all versions before 1.43.10, 1.45.5, and 1.46.1. |
| Impact | This is a stored cross-site scripting flaw (CWE-79) in the MediaWiki Thanks extension, rated CVSS 3.1 6.1 (Medium). All exploitation signals point to LOW real-world urgency rather than active priority: SSVC scores Exploitation as 'none', Automatable as 'no', and Technical Impact as 'partial', which is fully consistent with a stored-XSS bug that needs a victim to view attacker-influenced content. There is no EPSS score, no CISA KEV listing, and no public exploit identified at time of analysis. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) shows the required user interaction (UI:R - a victim must render the poisoned page) and a scope change (S:C, the injected script runs in the victim's browser context rather than the vulnerable server component), but only Low confidentiality and Low integrity impact and no availability impact - typical of reflected-into-DOM script execution rather than server compromise. One caveat: the vector asserts PR:N (unauthenticated), yet the Thanks extension's normal workflow (sending a 'thank' for an edit/log action) generally requires an account to store content, so on wikis that forbid anonymous actions the practical privilege requirement is likely PR:L - verify the exact injection sink against the Gerrit patch. Overall this is a genuine but low-priority, defense-in-depth fix, not a high-risk emergency. |
| Exploit ScenarioDerived | An attacker with the ability to trigger a Thanks action (or otherwise seed the vulnerable field) stores a crafted payload containing HTML/JavaScript. When another MediaWiki user - potentially an administrator - later loads the page or notification that renders the unescaped value, the script executes in their browser session, enabling session/token theft or actions performed as the victim. Requires victim interaction (viewing the page); no public exploit code is available and SSVC rates exploitation as 'none'. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Stored cross-site scripting in the MediaWiki Thanks extension (CWE-79) allows an authenticated user to persist a malicious script payload through a Thanks-related action or field, which then executes in the browser of any victim who later views the affected page or notification. All versions before 1.43.10, 1.45.5, and 1.46.1 are affected, and successful exploitation requires victim interaction with the rendered content; because the injected script executes in the victim's browser session, the CVSS 3.1 base score is 6.1 (Medium) with a scope change, but only low confidentiality and integrity impact and no availability impact. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment rates exploitation as none and automatable as no; vendor patches are available.
RemediationAI
Upgrade to a vendor-patched release: MediaWiki 1.43.10 (1.43.x branch), 1.45.5 (1.45.x branch), or 1.46.1 (1.46.x branch), whichever matches your installed version line - the fix is available from the vendor and the corresponding Gerrit change (I6d563f9cdab25c07dcd0083f3af2126e0859d098) is referenced in the CVE record alongside the Wikimedia Phabricator task T432424 at https://phabricator.wikimedia.org/T432424. If an immediate upgrade is not possible, the most effective compensating control is to disable the Thanks extension entirely by removing its load line (wfLoadExtension or require_once) from LocalSettings.php, which fully removes the attack surface at the cost of losing the thanks/notification feature; administrators should weigh whether that feature is worth the residual stored-XSS risk. Additional interim hardening includes restricting the ability to perform thanks actions or minimizing the number of untrusted accounts on the wiki, and applying a Content-Security-Policy or output-sanitizing layer that blocks inline script execution - recognizing that CSP can break legitimate wiki gadgets and is not a substitute for patching. Given the assessesd requirement for victim interaction and an authenticated storing user, and the absence of observed exploitation, patch deployment can follow normal maintenance windows rather than emergency change procedures.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a CWE-79 improper neutralization of input during web page generation in the MediaWiki Thanks extension, an optional-but-bundled MediaWiki feature that lets users send a 'thank' notification to another editor for a specific edit. The flaw lies in the extension's output handling: a value derived from a Thanks-related action or stored field is emitted into generated HTML without proper escaping, so attacker-controlled markup is rendered as script rather than text. Since MediaWiki extensions run inside the authenticated wiki interface, the injected payload inherits the victim's session context - this is reflected in the scope-change metric (S:C) - but the impact remains confined to browser-side script execution (C:L/I:L/A:N) rather than server compromise. The affected CPE is cpe:2.3:a:the_wikimedia_foundation:mediawiki_-_thanks_extension:*:*:*:*:*:*:*:*, with the fix landing in the 1.43.x, 1.45.x, and 1.46.x maintenance branches (1.43.10, 1.45.5, 1.46.1). Note that the vendor-published CVSS vector lists PR:N, while the independent assessment applies PR:L, reflecting that the storing action realistically requires an account and the extension's thank workflow; remediation and risk statements here follow the assessed PR:L / UI:R profile. The related CVE record is tracked under EUVD-2026-87204, with development discussion in Phabricator task T432424.
Know when Mediawiki Thanks Extension gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Storing the payload realistically requires a wiki account to perform a Thanks action (PR:L rather than PR:N); victim must render the content (UI:R); browser-context execution yields S:C with Low C/I and no availability impact.
Primary rating from Vendor (wikimedia-foundation).
CVSS VectorVendor: wikimedia-foundation
Lifecycle Timeline
2DescriptionCVE.org
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in The Wikimedia Foundation Mediawiki - Thanks Extension allows Stored XSS.
This issue affects Mediawiki - Thanks Extension: from * before 1.43.10/1.45.5/1.46.1.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-87204
GHSA-vfcj-hxgx-8jpc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB