Cross-Site Scripting (XSS) in moin (CVE-2020-15275)
Summary
Cross-site scripting in moin (CVE-2020-15275). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.9.11 or later.
Original description
The description as published by the source.
MoinMoin is a wiki engine. In MoinMoin before version 1.9.11, an attacker with write permissions can upload an SVG file that contains malicious javascript. This javascript will be executed in a user's browser when the user is viewing that SVG file on the wiki. Users are strongly advised to upgrade to a patched version. MoinMoin Wiki 1.9.11 has the necessary fixes and also contains other important fixes.
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-2020-15275 has been found in moin.
Risk of unauthorized operations or information disclosure.
What to do: upgrade moin to 1.9.11 or later.
If unsure, ask your IT team or search "moin CVE-2020-15275" on the vendor's site.
CVE-2020-15275 (moin) — CWE-79
Attack vector: remote (network-reachable)
Patched: 1.9.11 — 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) exists in moin.
Check the vendor advisory for the affected versions of moin.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.9.11.
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. Run grep -r 'moin' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'moin' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
moinを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade moin to 1.9.11ステージング環境で 1.9.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- report advisory.checkmarx.net
- web github.com
- web pypi.org