CVE-2026-58035: MediaWiki Special:Block XSS Vulnerability (CVSS 4.8)
MediaWiki contains a cross-site scripting (XSS) vulnerability in its Special:Block page interface that allows an authenticated user with administrative privileges to inject malicious scripts. When a victim visits the affected page after the attacker has crafted a malicious block, the injected code executes in the victim's browser in the context of the wiki. This is a reflected or stored XSS issue depending on how the input flows through the Special Block feature, and it requires both high-privilege attacker account and user interaction to successfully exploit.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 4.8 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
- Weaknesses (CWE)
- CWE-79
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-07-01 / 2026-07-09
NVD description (verbatim)
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files resources/src/mediawiki.Special.Block/SpecialBlock.Vue.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-58035 is an Improper Neutralization of Input During Web Page Generation vulnerability (CWE-79) located in the SpecialBlock.Vue component within MediaWiki's resources/src/mediawiki.Special.Block directory. The vulnerability occurs because user-supplied input is not properly sanitized before being rendered in the HTML context of the Special:Block administrative page. An authenticated user holding administrative or blocking privileges can craft input that bypasses output encoding, allowing arbitrary JavaScript execution in the context of other administrators' sessions or browsers. The Vue.js component fails to apply adequate input validation or output encoding mechanisms when processing block-related form parameters.
Business impact
Successful exploitation could allow an attacker with admin-level access to compromise other administrators' sessions, steal session cookies or authentication tokens, perform unauthorized administrative actions on behalf of victims, or distribute malware to wiki maintainers and operators. For large or critical wiki installations, this could lead to data modification, user account compromise, or defacement. The impact is limited to high-privilege users, reducing the overall risk surface, but the context of wiki administration makes such accounts high-value targets.
Affected systems
MediaWiki instances are affected by this vulnerability. The specific vulnerable component is the Special:Block page interface (SpecialBlock.Vue). Organizations running MediaWiki for documentation, knowledge bases, or collaborative platforms should assess their deployment versions. Determine if your MediaWiki installation includes the affected SpecialBlock.Vue file and verify against the vendor advisory to confirm which versions contain the vulnerability.
Exploitability
Exploitation requires an authenticated account with administrative block privileges (high privilege requirement) and user interaction from a target administrator (they must visit a specially crafted link or block page). The attack vector is network-based with low complexity. While the barrier to entry is high due to privilege and user interaction requirements, the attack is straightforward once those conditions are met—no complex bypass techniques are needed beyond injecting script payloads into block parameters. The CVSS score of 4.8 (Medium) reflects these limiting factors.
Remediation
Apply security patches released by the Wikimedia Foundation for MediaWiki. Implement input validation and output encoding on all user-supplied data processed by the Special:Block component. Verify patches against the official Wikimedia security advisory to confirm the specific versions that resolve this issue. Until patches are applied, limit Special:Block access to a minimal set of highly trusted administrators and consider disabling the feature if not actively used.
Patch guidance
Consult the Wikimedia Foundation security advisories and release notes to identify the patched MediaWiki version that addresses CVE-2026-58035. Apply patches according to your maintenance schedule, prioritizing systems where block management is frequently performed by multiple administrators. Test patches in a staging environment to ensure Vue.js component compatibility with your MediaWiki extensions before production deployment.
Detection guidance
Monitor web server and application logs for suspicious activity on the Special:Block page, such as unusual parameters, encoded JavaScript snippets, or script-like payloads in block-related POST requests. Look for event log entries showing unexpected changes initiated by administrators or unusual admin-to-admin interactions. Implement Content Security Policy (CSP) headers to mitigate XSS impact even if injection occurs. Review recent block entries and check for signs of tampering or administrative actions performed by compromised accounts.
Why prioritize this
Although rated MEDIUM severity (CVSS 4.8), this vulnerability warrants prompt attention because it targets administrative interfaces where attackers can move laterally between high-privilege accounts. The Vue.js component handling indicates a modern tech stack that may be actively developed and widely deployed. However, the requirement for existing high-privilege access and user interaction limits immediate threat. Prioritize patching for wikis with multiple administrators and high-value content; isolated single-admin wikis face lower risk.
Risk score, explained
The CVSS 3.1 score of 4.8 reflects a Medium severity rating based on: network-accessible attack vector (AV:N), low attack complexity (AC:L), but high privileges required to exploit (PR:H) and user interaction needed (UI:R). Impact is limited to confidentiality and integrity (C:L, I:L) with no availability impact (A:N). Scope is changed (S:C), meaning the vulnerability can affect resources beyond the vulnerable component. The high-privilege and user-interaction requirements prevent a higher score despite the nature of the attack.
Frequently asked questions
Does this vulnerability affect all MediaWiki users or only administrators?
Only authenticated users with administrative block privileges can exploit this vulnerability. Regular wiki editors and anonymous users cannot trigger it. However, any administrator could be victimized if they visit a malicious link crafted by an attacker admin. The impact is primarily to the administrator community of a wiki.
Is this vulnerability currently being exploited in the wild?
No—this vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, indicating no public evidence of active exploitation as of the publication date. However, absence from KEV does not guarantee zero real-world use; security teams should still treat it as a credible threat requiring timely patching.
What is the difference between this XSS and other web application XSS vulnerabilities?
This XSS occurs specifically in a Vue.js component used for administrative block management rather than in general user-facing content. It requires privileges to set the XSS payload (via block parameters) and user interaction from another admin to execute it. Many public wiki XSS vulnerabilities are stored or reflected in user content areas and can be triggered by any visitor, making them higher severity.
Can I mitigate this while waiting for patches?
Yes. Restrict the Special:Block feature to only the most trusted administrators, reduce the number of block-capable accounts, educate admins about not clicking suspicious links pointing to block pages, and deploy Content Security Policy headers to limit inline script execution. These are temporary measures; patching remains essential.
This analysis is based on the CVE record and vendor information available as of the publication date. Patch version numbers and specific remediation steps must be verified against the official Wikimedia Foundation security advisory and release notes. No exploit code or weaponized proof-of-concept is provided. Organizations should conduct their own risk assessment based on their MediaWiki version, deployment scope, and administrative user count. This vulnerability is not currently listed as actively exploited, but that status may change; prioritize patching based on your risk profile and change management process. Source: NVD (public-domain), retrieved 2026-08-10. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-14358MEDIUMMediaWiki Charts Extension XSS Vulnerability – Patch Guide
- CVE-2026-58028MEDIUMMediaWiki XSS Vulnerability in API and Page Rendering
- CVE-2026-58030MEDIUMXSS Vulnerability in Wikimedia SyntaxHighlight_GeSHi Extension
- CVE-2026-58031MEDIUMMediaWiki API Sandbox XSS Vulnerability (CVSS 5.4)
- CVE-2026-58032MEDIUMMediaWiki XSS Vulnerability in API Module – Patch Guidance
- CVE-2026-58034MEDIUMCheckUser Cross-Site Scripting (XSS) Vulnerability in MediaWiki
- CVE-2026-58037MEDIUMMediaWiki Cross-Site Scripting (XSS) in Log Formatters and Language Components
- CVE-2026-58038MEDIUMMediaWiki Timeline XSS Vulnerability—CVSS 6.1 Patch Guidance