Cross-Site Scripting (XSS) in indico (CVE-2026-107397)
Summary
Cross-site scripting in indico (CVE-2026-107397). Risk of unauthorized operations or information disclosure. Exploitable via indico.conf. Mitigation: upgrade to 3.3.13 or later.
Original description
The description as published by the source.
Impact
There is a Cross-Site-Scripting vulnerability in the minute editor conflict UI tha's shown when concurrent edits are made to the same minutes in an event.
Patches
You should to update to Indico 3.3.13 as soon as possible.
See the docs for instructions on how to update.
Workarounds
- Set
CSP_ENABLED = Trueinindico.conf- this is recommended regardless of updating. - Only let trustworthy users create content (including minutes which speakers can typically do as well) on Indico.
For more information
If you have any questions or comments about this advisory:
- Open a thread in our forum
- Email us privately at indico-team@cern.ch
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-107397 has been found in indico.
Attackers can target a specific entry point like indico.conf over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: upgrade indico to 3.3.13 or later.
If unsure, ask your IT team or search "indico CVE-2026-107397" on the vendor's site.
CVE-2026-107397 (indico) — CWE-79 / CVSS v3 4.4
Attack vector: remote (network-reachable)
Attack surface: indico.conf
Patched: 3.3.13 — apply immediately
Workaround: set CSP_: ENABLED
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 indico.conf.
Check the vendor advisory for the affected versions of indico. Attack surface: indico.conf.
Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.
Update to 3.3.13.
Workaround: set CSP_: ENABLED
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 temporary workaround mitigate
set CSP_: ENABLEDパッチが適用されるまでの応急処置として、set CSP_: ENABLED を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade indico to 3.3.13ステージング環境で 3.3.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。