Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain ability to save WikiLambda content
-
DeliveryInject unneutralized XSS payload into ZObject
-
ExploitPayload stored server-side
-
ExecutionVictim views WikiLambda page
-
PersistScript executes in victim browser (S:C)
-
ImpactSession/token theft or actions 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 | Requires the Wikimedia MediaWiki WikiLambda extension (the software behind Wikifunctions/Abstract Wikipedia) at a version before 1.46.1. The attacker must be able to store content processed by WikiLambda (e.g., a ZObject / function definition) containing an unneutralized script payload, and a victim must subsequently view the rendered page (UI:R). Limiting factors: exploitation depends on this specific, narrowly-deployed extension being installed; impact is bounded to Low C/I with no availability effect; the vendor vector lists PR:N but in practice saving stored content typically requires an authenticated editing account, further constraining who can plant the payload. Highest-value outcome is hitting a privileged (admin) viewer. |
| Impact | This is a moderate-severity Stored XSS (CVSS 6.1) that behaves as a genuine-but-low-urgency issue rather than an emergency. The signals are consistent and point the same direction: CISA's SSVC framework rates Exploitation as 'none' (no known exploitation), Automatable as 'no', and Technical Impact as 'partial' - all of which align with a scope-changing but limited-impact XSS. 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 network reach with low complexity but requires victim interaction (UI:R) and yields only Low confidentiality/integrity impact with a changed scope (attacker script executing in the victim's browser session against the wiki origin). One notable tension: the vector claims PR:N (unauthenticated), yet a Stored XSS in a MediaWiki content extension typically requires the attacker to first save malicious content (ZObjects/function definitions in WikiLambda), which normally needs edit privileges - verify with vendor whether unauthenticated content storage is truly possible, otherwise PR:L is more realistic. The self-report by the Wikimedia Foundation with an available patch and Gerrit changeset indicates a responsibly disclosed, vendor-fixed defect rather than an actively exploited one. |
| Exploit ScenarioDerived | An attacker with the ability to save WikiLambda content (a function, implementation, or other ZObject) injects a crafted payload that is not properly neutralized during page generation, so it is stored and later rendered as executable script. When another user - potentially an administrator - views the affected WikiLambda page, the script runs in their browser under the wiki's origin, enabling session/token theft or actions in the victim's authenticated context. No public exploit code has been identified, and successful attack requires a victim to view the poisoned page (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Stored cross-site scripting in the Wikimedia MediaWiki WikiLambda extension (the software behind Wikifunctions / Abstract Wikipedia) allows an attacker who can store content processed by the extension - such as a ZObject function definition - to have an unneutralized script payload executed in the browser of any user who later views the rendered page. Only installations running the WikiLambda extension at a version before 1.46.1 are affected, which is a narrowly deployed component, and impact is bounded to low confidentiality and integrity with no availability effect (CVSS 6.1, assessed vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N). No public exploit code has been identified at time of analysis, no CISA KEV listing applies, and CISA SSVC rates exploitation as none and automatable as no, so this is a genuine but low-urgency issue rather than an emergency; the highest-value outcome for an attacker is planting a payload that is later rendered to a privileged administrator.
RemediationAI
Vendor-released patch: upgrade the WikiLambda extension to 1.46.1 or later; the fix is tracked in the Wikimedia Phabricator task https://phabricator.wikimedia.org/T428829 and delivered through the Gerrit change https://gerrit.wikimedia.org/r/c/1307827, and the authoritative advisory pointer is https://nvd.nist.gov/vuln/detail/CVE-2026-103046. Because the vendor has published a fix, patching is the primary and preferred action, and sites should confirm the extension version actually in use rather than assuming MediaWiki core updates cover the extension. If immediate upgrade is not possible, the most effective compensating control is to disable or uninstrument the WikiLambda extension on installations that do not need Wikifunctions functionality - the trade-off is complete loss of Abstract Wikipedia/ZObject features and, on Wikimedia production wikis, that is not a viable option. A narrower control is to restrict who may create or edit ZObjects and related WikiLambda content to a tight, trusted group (for example by tightening edit permissions on the relevant namespaces and Special pages); this reduces the pool of potential payload planters but does not eliminate the risk from an already-trusted insider or a compromised trusted account, and it does not protect viewers if a payload is already stored. Deploying a restrictive Content-Security-Policy on the wiki reduces the chance that an injected inline script executes but may break legitimate extensions and gadget scripts, so it should be tested before rollout. Finally, because the payload is stored, review and clean any pre-existing suspicious ZObject revisions after patching, and treat the vulnerability as moderate severity pending confirmation that no exploitation has occurred.
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 WikiLambda extension for MediaWiki. WikiLambda implements the Wikifunctions / Abstract Wikipedia data model, where user-authored ZObjects - functions, implementations, testers, and their typed arguments - are stored in the wiki and rendered back into normal wiki pages and Special pages. If the extension emits any of that stored ZObject content into HTML without context-appropriate output encoding or escaping, the markup is persisted and re-executed every time a viewer loads the rendered page, making this a classic stored (persistent) XSS rather than a reflected one. The CVSS scope-change component reflects that script executing in the origin of the wiki can reach beyond the vulnerable component's own security scope - for example, reading DOM content or acting with a viewer's session context on that wiki. UI:R is present because a victim must actually view the rendered page for the payload to fire, and AV:N/AC:L describe a network-reachable, low-complexity trigger; the vendor vector carries PR:N while our independent assessment and the practical editing workflow suggest the more realistic prerequisite is an account able to save the stored content (PR:L), so authentication requirements should be treated as contested between the two vectors. CPE data identifies the affected component precisely as cpe:2.3:a:the_wikimedia_foundation:mediawiki_-_wikilambda_extension, meaning only MediaWiki instances with the WikiLambda extension installed and enabled are in scope, not MediaWiki core.
Know when Mediawiki 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 requiring a victim to view the page (UI:R) and a scope change into the browser (S:C); PR:L because storing WikiLambda content realistically needs an editing account.
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 Wikimedia Foundation MediaWiki - WikiLambda extension allows Stored XSS.
This issue affects MediaWiki - WikiLambda extension: before 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.
MediaWiki 1.22.x before 1.22.2, 1.21.x before 1.21.5, and 1.19.x before 1.19.11, when DjVu or PDF file upload support is
The MWOAuthDataStore::lookup_token function in Extension:OAuth for MediaWiki 1.25.x before 1.25.3, 1.24.x before 1.24.4,
An issue was discovered in the CheckUser extension for MediaWiki through 1.39.3. Rated critical severity (CVSS 9.8), thi
The admin API module in the QuizGame extension for MediaWiki through 1.37.2 (before 665e33a68f6fa1167df99c0aa18ed0157cdf
The SemanticDrilldown extension for MediaWiki through 1.37.2 (before e688bdba6434591b5dff689a45e4d53459954773) allows SQ
An issue was discovered in MediaWiki through 1.37.1. Rated critical severity (CVSS 9.8), this vulnerability is remotely
An issue was discovered in MediaWiki through 1.37.1. Rated critical severity (CVSS 9.8), this vulnerability is remotely
An issue was discovered in the CentralAuth extension in MediaWiki through 1.36. Rated critical severity (CVSS 9.8), this
An issue was discovered in the AbuseFilter extension in MediaWiki through 1.36. Rated critical severity (CVSS 9.8), this
api.php in MediaWiki before 1.27.4, 1.28.x before 1.28.3, and 1.29.x before 1.29.2 has a Reflected File Download vulnera
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in The Wikimedia Foun
An issue was discovered in the FileImporter extension in MediaWiki through 1.36. Rated high severity (CVSS 8.8), this vu
EUVD-2026-89478
GHSA-wgjv-5xcv-4jq5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB