Cross-Site Scripting (XSS) in Mediawiki - WikiLambda Extension (CVE-2026-100383)
Summary
Cross-site scripting in Mediawiki - WikiLambda Extension (CVE-2026-100383). Risk of unauthorized operations or information disclosure. Exploitable via master.
Original description
The description as published by the source.
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Wikimedia Foundation Mediawiki - WikiLambda Extension allows Cross-Site Scripting (XSS).
This issue affects Mediawiki - WikiLambda Extension: 1.47.0-alpha. The issue has been remediated on the master branch.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-100383 has been found in Mediawiki - WikiLambda Extension.
Attackers can target a specific entry point like master over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Mediawiki - WikiLambda Extension CVE-2026-100383" on the vendor's site.
CVE-2026-100383 (Mediawiki - WikiLambda Extension) — CWE-79
Attack surface: master
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in Mediawiki - WikiLambda Extension. Attackers reach the vulnerable code path via master.
Check the vendor advisory for the affected versions of Mediawiki - WikiLambda Extension. Attack surface: master.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Mediawiki - WikiLambda Extension を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web gerrit.wikimedia.org
- web phabricator.wikimedia.org
- web nvd.nist.gov
- web github.com