Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain wiki edit capability
-
DeliveryInject script into Refreshed-rendered field
-
ExploitPayload stored in wiki
-
ExecutionVictim renders affected page
-
ImpactScript executes in victim browser session
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 that the installation use the Wikimedia 'Refreshed' skin (a non-default, third-party MediaWiki skin) at a version before 1.46.1 / 1.45.5 / 1.43.10, and that an attacker can save content into the field the skin renders unsafely. Realistic exploitation is LIMITED by: (1) required user interaction - a victim must load the page containing the stored payload (UI:R); (2) edit access - although the vector is PR:N, storing the payload needs some ability to save wiki content, which on edit-restricted wikis means an authenticated editor; (3) deployment scope - only wikis that have installed and enabled the Refreshed skin are affected. Impact is bounded to in-browser script execution (C:L/I:L, no availability impact). |
| Impact | Signals are consistently LOW-to-MODERATE and non-urgent. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, 6.1 Medium) describes a classic stored XSS: network-reachable, low complexity, but requiring victim interaction (UI:R) and yielding only low confidentiality/integrity impact with a scope change into the victim's browser. CISA SSVC reinforces this as non-priority - Exploitation: none (no observed activity), Automatable: no (requires a victim to render the poisoned page), Technical Impact: partial. No EPSS score, no KEV listing, and no public POC were provided, so there is no evidence of exploitation or weaponization: no public exploit identified at time of analysis. The one tension worth flagging is PR:N on a STORED XSS - storing a payload usually needs some edit capability; the vendor rates it unauthenticated, which is defensible on open/anonymous-editable MediaWiki wikis but would effectively require authentication on wikis that restrict editing (verify against your wiki's editing permissions). Net: a legitimate issue to patch on a normal cadence, not an emergency; the dominant real-world factor is that the affected component is a niche skin, sharply limiting the exposed population. |
| Exploit ScenarioDerived | An attacker with the ability to save wiki content (anonymous on open wikis, or a registered editor on restricted ones) injects a crafted payload into a field rendered by the Refreshed skin. When another user - potentially an administrator - later views the affected page, the stored script executes in their browser session under the wiki's origin, enabling session/cookie theft or UI actions on their behalf. No public exploit code or active exploitation is known at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Stored cross-site scripting in the MediaWiki 'Refreshed' skin lets an attacker who can save wiki content plant script that executes in the browser of any user viewing the affected page, affecting all versions before 1.46.1, 1.45.5, and 1.43.10 of this non-default, opt-in third-party skin. The CVSS 3.1 base score is 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), which bounds impact to in-browser script execution - low confidentiality and integrity, no availability - once a victim loads the tainted page. Exposure is limited to wikis that have installed and enabled Refreshed; CISA's SSVC assessment records exploitation as none with partial technical impact, and no public exploit has been identified at time of analysis. Vendor patches are available.
RemediationAI
Vendor-released patch: upgrade the Refreshed skin to 1.46.1, 1.45.5, or 1.43.10 according to the branch in use (upstream fix via Gerrit change 1309277, tracked in Phabricator T268377). If the upgrade cannot be applied immediately, disable the Refreshed skin in the MediaWiki skin configuration (remove it from the enabled/default skin settings so pages are no longer rendered by it); the trade-off is the immediate loss of that skin's appearance and any site customizations built on it. Because the payload is stored, restrict who can save wiki content and require review or moderation of edits - this lowers likelihood on open wikis but does not eliminate exposure where untrusted users can already edit. A Content-Security-Policy that forbids inline script can blunt execution in supporting browsers, though it risks breaking legitimate skin and gadget JavaScript and should be tested before enforcement. After patching, audit page content for any payloads left behind by earlier exploitation and remove them, and review sessions/accounts of users who viewed affected pages for signs of script-driven activity.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-79, improper neutralization of input during web page generation, in the MediaWiki Refreshed skin: user-supplied content is rendered into HTML without adequate escaping at the point the skin builds the page, so a stored payload is emitted for every visitor rather than reflected only back to the submitter. MediaWiki skins are the presentation layer (PHP templates, HTML, and front-end assets) sitting on top of core parser output; Refreshed is a Wikimedia-maintained but non-default, opt-in skin, which is why the NVD CPE entry is scoped to cpe:2.3:a:the_wikimedia_foundation:mediawiki_-_refreshed_skin:*:*:*:*:*:*:*:* with a wildcard version field. That wildcard means the CPE cannot pin the vulnerable range on its own; the authoritative bounds come from the vendor advisory and the ENISA EUVD record - versions before 1.46.1 on the current branch, before 1.45.5 on the 1.45 branch, and before 1.43.10 on the 1.43/LTS branch. The CVSS vector's S:C (scope change) reflects that injected script runs in the wiki's origin context, i.e. against the site and its users, while C:L/I:L/A:N keeps impact to low confidentiality and integrity with no availability effect. UI:R reflects that a victim must load the poisoned page; although the vector is PR:N, the assessed exploitation conditions note that storing the payload in practice requires some ability to save wiki content, which on edit-restricted wikis means an authenticated editor.
Know when Mediawiki Refreshed Skin 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
Network-reachable stored XSS executing in a victim's browser (UI:R, S:C) with limited confidentiality/integrity impact; PR:N retained per vendor though edit access is practically needed on restricted wikis.
Primary rating from Vendor (wikimedia-foundation).
CVSS VectorVendor: wikimedia-foundation
Lifecycle Timeline
3DescriptionCVE.org
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in The Wikimedia Foundation Mediawiki - Refreshed skin allows Stored XSS.
This issue affects Mediawiki - Refreshed skin: before 1.46.1, 1.45.5, 1.43.10.
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-89485
GHSA-7j9q-53xp-5mqq
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB