Skip to main content

MediaWiki Flow Extension CVE-2026-100238

| EUVDEUVD-2026-89033 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-09-29 wikimedia-foundation GHSA-hg46-8gx2-qp79
6.1
CVSS 3.1 · Vendor: wikimedia-foundation
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain posting access to Flow board
  2. Delivery
    Submit topic/reply with crafted XSS payload
  3. Exploit
    Payload stored unneutralized
  4. Execution
    Victim views discussion board
  5. Persist
    Script executes in victim browser
  6. Impact
    Session/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 a MediaWiki installation with the Flow / StructuredDiscussions extension enabled (an optional, now largely deprecated extension - not present on default MediaWiki installs), at a version before 1.46.1, 1.45.5, or 1.43.10. The attacker needs the ability to post content to a Flow discussion board (topics/replies), which on typical wikis means a registered account, though wikis permitting anonymous edits lower this barrier. Exploitation is limited by required victim interaction (UI:R): another user must view the board containing the stored payload for the script to execute; impact is confined to that victim's browser session (C:L/I:L, no availability impact).

Impact

This is a moderate-severity stored XSS with signals that consistently point to low-to-moderate real-world priority rather than an urgent threat. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, score 6.1) describes network-reachable, low-complexity injection whose impact is bounded to low confidentiality and integrity in the victim's browser context, with the S:C scope change reflecting that injected script executes outside the extension's own security boundary. CISA's SSVC decision framework corroborates low urgency: Exploitation=none (no observed or public exploitation), Automatable=no, and Technical Impact=partial. There is no EPSS score, no CISA KEV listing, and no public proof-of-concept in the provided data, so exploitation status is 'no public exploit identified at time of analysis' - this should not be conflated with active exploitation. The one conflicting nuance is the PR:N rating: the vendor rates it unauthenticated, but stored XSS in a Flow discussion board generally requires the ability to post content, which on many MediaWiki deployments requires at least a registered account (anonymous editing is configurable and common, which makes PR:N defensible but deployment-dependent). Overall this is a standard high-ish-CVSS-but-moderate-real-risk web vulnerability: a patch exists, impact is partial, and no exploitation is observed.

Exploit ScenarioDerived

An attacker who can post to a MediaWiki Flow (StructuredDiscussions) board submits a discussion topic or reply containing a crafted payload that bypasses output neutralization. When another user - potentially a moderator or administrator - views the board, the stored script executes in their browser session, enabling session/token theft or actions in their context. No public proof-of-concept is identified at time of analysis, and exploitation requires a victim to view the malicious content (UI:R).

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 01, 2026

Stored cross-site scripting in the MediaWiki Flow (StructuredDiscussions) extension lets a user who can post content to a Flow discussion board inject script that executes in the browser of any other user who later views that board. The flaw affects installations running the extension at versions before 1.46.1, 1.45.5, and 1.43.10; Flow is an optional, largely deprecated extension and is not present on a default MediaWiki install. No public exploit code has been identified and CISA's SSVC assessment records no exploitation, so this is a moderate-severity, low-to-moderate-priority issue, with vendor patches already available.

RemediationAI

Vendor-released patches are available: upgrade the Flow (StructuredDiscussions) extension to 1.46.1, 1.45.5, or 1.43.10 according to the MediaWiki release branch in use, applying the upstream fix described in Gerrit change Ic6149363fe1de2440240fe88aebfd4ae30cea606 and tracked in Phabricator task T432425 (https://phabricator.wikimedia.org/T432425). If upgrading is not immediately possible, the most effective compensating control is to disable the Flow/StructuredDiscussions extension entirely, since it is optional and largely deprecated rather than core MediaWiki - the trade-off is loss of structured discussion boards on affected wikis and potential disruption to existing Flow content. Where the extension must stay enabled, restrict the ability to create topics and replies to a small trusted group by tightening the relevant MediaWiki user rights and disabling anonymous edits, which removes the easiest posting path for an attacker; the trade-off is reduced wiki openness and extra administrative overhead, and it does not eliminate the flaw for legitimate but compromised accounts. Note that blocking or filtering request parameters is unlikely to help, because the defect lies in how stored content is rendered; because exploitation requires a victim to view the poisoned board (UI:R), limiting exposure to boards via read restrictions can add defense in depth but is not a substitute for patching.

Affected VersionsENISA

Mediawiki - Flow Extension * <1.46.1, 1.45.5, 1.43.10

Affected Packages

euvd mediawiki_flow_extension_1_46_1_1_45_5 no fix

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. The Flow (StructuredDiscussions) extension adds a structured, topic-and-reply discussion system to MediaWiki, storing user-submitted text as wiki content that is subsequently rendered back into discussion board pages. Because stored content is not correctly escaped or sanitized at render time, an attacker with the ability to post to a board can persist markup that browsers interpret as script when another user opens the affected board - the defining pattern of stored (persistent) XSS. The affected component is tracked as cpe:2.3:a:wikimedia_foundation:mediawiki_-_flow_extension:*:*:*:*:*:*:*:*, owned by the Wikimedia Foundation. The assessed CVSS vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) indicates the attacker needs prior access to post content (PR:L) and that a victim must interact by viewing the board (UI:R); the changed scope (S:C) reflects that the injected script runs in the security context of the wiki origin, so it can act on behalf of the victim's session even though direct confidentiality and integrity impact on the vulnerable component itself is low. Exploitation is confined to the victim's browser session with no availability impact, and the fix is being developed publicly through Phabricator task T432425 and Gerrit change Ic6149363fe1de2440240fe88aebfd4ae30cea606.

Know when Mediawiki Flow 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

Vendor (wikimedia-foundation) PRIMARY 6.1 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
vuln.today AI 5.4 MEDIUM

Stored XSS reachable over the network; posting to a Flow board generally needs a low-privileged account (PR:L), a victim must view the content (UI:R), and script runs cross-context (S:C) for low C/I impact.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (wikimedia-foundation).

CVSS VectorVendor: wikimedia-foundation

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

3
CVSS changed
Sep 30, 2026 - 22:08 NVD
6.1 (None) 6.1 (MEDIUM)
Patch available
Sep 29, 2026 - 17:17 EUVD
CVE Published
Sep 29, 2026 - 16:12 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Wikimedia Foundation Mediawiki - Flow Extension allows Stored XSS.

This issue affects Mediawiki - Flow Extension: from * before 1.46.1, 1.45.5, 1.43.10.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Medium
optional, largely deprecated extension on the otherwise ubiquitous MediaWiki engine
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy