Citizen allows stored XSS in Command Palette tip messages
Summary
Cross-site scripting reported (CVE-2025-49575). Confidential information can be exposed externally. Exploitable via editinterface. Mitigation: upgrade to 3.3.1 or later.
Original description
The description as published by the source.
Citizen is a MediaWiki skin that makes extensions part of the cohesive experience. Multiple system messages are inserted into the CommandPaletteFooter as raw HTML, allowing anybody who can edit those messages to insert arbitrary HTML into the DOM. This impacts wikis where a group has the editinterface but not the editsitejs user right. This vulnerability is fixed in 3.3.1.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2025-49575 has been found.
Attackers can target a specific entry point like editinterface over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade the affected software to 3.3.1 or later.
If unsure, ask your IT team or search "CVE-2025-49575" on the vendor's site.
CVE-2025-49575 — CWE-79
Attack vector: remote (network-reachable) / no user interaction
Attack surface: editinterface / editsitejs
Patched: 3.3.1 — apply immediately
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) has been reported. Attackers reach the vulnerable code path via editinterface.
Check the vendor advisory for the affected versions. Attack surface: editinterface / editsitejs.
Severity: ?. Confidential information can be exposed externally.
Update to 3.3.1.
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・依存マニフェストで影響コンポーネントを特定する。
-
2Apply patch patch
Upgrade to 3.3.1ステージング環境で 3.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com