CVE-2026-30977
Received Received - Intake
Stored XSS in MediaWiki RenderBlocking Extension Before

Publication date: 2026-03-10

Last updated on: 2026-03-10

Assigner: GitHub, Inc.

Description
RenderBlocking is a MediaWiki extension that allows interface administrators to specify render-blocking CSS and JavaScript. Prior to 0.1.1, there is Stored XSS in renderblocking-css with Inline Assets mode. $wgRenderBlockingInlineAssets = true and editsitecss user rights are required. This vulnerability is fixed in 0.1.1.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-10
Last Modified
2026-03-10
Generated
2026-05-07
AI Q&A
2026-03-10
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
lihaohong renderblocking to 0.1.0 (inc)
lihaohong renderblocking 0.1.1
mediawiki renderblocking to 0.1.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

[{'type': 'paragraph', 'content': 'CVE-2026-30977 is a stored Cross-Site Scripting (XSS) vulnerability in the RenderBlocking MediaWiki extension when used with Inline Assets mode enabled. It occurs because malicious CSS content injected by a user with the "editsitecss" permission is not properly sanitized before being rendered. This allows the attacker to embed scripts that execute in the browsers of other users viewing the affected CSS pages.'}, {'type': 'paragraph', 'content': 'The vulnerability arises from the use of unsafe methods to insert CSS and JavaScript inline into the page head, specifically using Html::rawElement, which allowed raw HTML injection. The issue was fixed by replacing these calls with safer methods that properly encode and sanitize the inline assets.'}] [1, 3]


How can this vulnerability impact me? :

[{'type': 'paragraph', 'content': 'This vulnerability allows a user with high privileges (specifically the "editsitecss" permission) to inject malicious scripts into global CSS pages. These scripts then execute in the browsers of other users who view the affected pages.'}, {'type': 'paragraph', 'content': 'The impact is considered low severity, with potential low confidentiality and integrity risks. It could lead to unauthorized script execution, which might be used to steal information or manipulate the user interface, but it does not affect system availability.'}] [2, 3]


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': "This vulnerability involves stored Cross-Site Scripting (XSS) in MediaWiki's RenderBlocking extension when Inline Assets mode is enabled and a user with the editsitecss permission injects malicious content into CSS pages."}, {'type': 'paragraph', 'content': 'To detect this vulnerability, you should check if your MediaWiki installation uses RenderBlocking extension version 0.1.0 or earlier with the setting $wgRenderBlockingInlineAssets set to true.'}, {'type': 'paragraph', 'content': "You can inspect the content of the MediaWiki:Renderblocking.css page or other CSS pages editable by users with editsitecss rights for suspicious injected scripts such as sequences like '</style><script>alert(1)</script><style>'."}, {'type': 'paragraph', 'content': 'Since this is a stored XSS vulnerability, network detection might be limited, but you can use commands or scripts to fetch and scan the CSS pages for suspicious inline scripts.'}, {'type': 'list_item', 'content': 'Use curl or wget to retrieve the CSS page content, for example: curl -s https://yourwiki.example.com/wiki/MediaWiki:Renderblocking.css'}, {'type': 'list_item', 'content': "Search for suspicious script tags or unusual inline JavaScript using grep or similar tools: grep -E '</style><script|<script>alert' Renderblocking.css"}, {'type': 'list_item', 'content': 'Check the RenderBlocking extension version installed by querying your MediaWiki extensions or checking the version file.'}] [3]


What immediate steps should I take to mitigate this vulnerability?

The primary mitigation step is to upgrade the RenderBlocking extension to version 0.1.1 or later, where the vulnerability is fixed.

This update replaces unsafe raw HTML insertion methods with safe inline style and script encoding, preventing malicious script injection.

Additionally, restrict the editsitecss user rights to trusted administrators only, as the vulnerability requires this permission to exploit.

If upgrading immediately is not possible, consider disabling the Inline Assets mode by setting $wgRenderBlockingInlineAssets to false to prevent the vulnerability from being triggered.

Review and sanitize existing CSS pages editable by users with editsitecss rights to remove any injected malicious scripts.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart