Cross-Site Scripting (XSS) in indico (CVE-2026-25739)
Summary
Cross-site scripting in indico (CVE-2026-25739). Risk of unauthorized operations or information disclosure. Exploitable via STATIC_FILE_METHOD. Mitigation: upgrade to 3.3.10 or later.
Original description
The description as published by the source.
Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. Versions prior to 3.3.10 are vulnerable to cross-site scripting when uploading certain file types as materials. Users should upgrade to version 3.3.10 to receive a patch. To apply the fix itself updating is sufficient, but to benefit from the strict Content Security Policy (CSP) Indico now applies by default for file downloads, update the webserver config in case one uses nginx with Indico's STATIC_FILE_METHOD set to xaccelredirect. For further directions, consult the GitHub Security advisory or Indico setup documentation. Some workarounds are available. Use the webserver config to apply a strict CSP for material download endpoints, and/or only let trustworthy users create content (including material uploads, which speakers can typically do as well) on Indico.
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-2026-25739 has been found in indico.
Attackers can target a specific entry point like STATIC_FILE_METHOD over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade indico to 3.3.10 or later.
If unsure, ask your IT team or search "indico CVE-2026-25739" on the vendor's site.
CVE-2026-25739 (indico) — CWE-79
Attack vector: remote (network-reachable)
Attack surface: STATIC_FILE_METHOD / xaccelredirect
Patched: 3.3.10 — 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 indico. Attackers reach the vulnerable code path via STATIC_FILE_METHOD.
Check the vendor advisory for the affected versions of indico. Attack surface: STATIC_FILE_METHOD / xaccelredirect.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.3.10.
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 'indico' . 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 'indico' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
indicoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade indico to 3.3.10ステージング環境で 3.3.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com