Search for packages
| purl | pkg:pypi/indico@2.0rc2 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-3ev2-cjep-w3fd
Aliases: CVE-2024-45399 GHSA-rrqf-w74j-24ff PYSEC-2024-90 |
Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. In Indico prior to version 3.3.4, corresponding to Flask-Multipass prior to version 0.5.5, there is a Cross-Site-Scripting vulnerability during account creation when redirecting to the `next` URL. Exploitation requires initiating the account creation process with a maliciously crafted link, and then finalizing the signup process. Because of this, it can only target newly created (and thus unprivileged) Indico users. Indico 3.3.4 upgrades the dependency on Flask-Multipass to version 0.5.5, which fixes the issue. Those who build the Indico package themselves and cannot upgrade can update the `flask-multipass` dependency to `>=0.5.5` which fixes the vulnerability. Otherwise one could configure one's web server to disallow requests containing a query string with a `next` parameter that starts with `javascript:`. |
Affected by 7 other vulnerabilities. |
|
VCID-cjkd-nkad-b7a8
Aliases: GHSA-67cx-rhhq-mfhq GMS-2019-111 |
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in indico. |
Affected by 9 other vulnerabilities. Affected by 10 other vulnerabilities. |
|
VCID-m3r7-uja3-ybge
Aliases: CVE-2025-59034 GHSA-4269-mcfh-cp7q |
Indico may disclose unauthorized user details access via legacy API A legacy API to retrieve user details could be misused to retrieve profile details of other users without having admin permissions due to a broken access check. |
Affected by 4 other vulnerabilities. |
|
VCID-n2kf-a5f2-h7d2
Aliases: CVE-2023-37901 GHSA-fmqq-25x9-c6hm PYSEC-2023-129 |
Indico is an open source a general-purpose, web based event management tool. There is a Cross-Site-Scripting vulnerability in confirmation prompts commonly used when deleting content from Indico. Exploitation requires someone with at least submission privileges (such as a speaker) and then someone else to attempt to delete this content. Considering that event organizers may want to delete suspicious-looking content when spotting it, there is a non-negligible risk of such an attack to succeed. The risk of this could be further increased when combined with some some social engineering pointing the victim towards this content. Users need to update to Indico 3.2.6 as soon as possible. See the docs for instructions on how to update. Users who cannot upgrade should only let trustworthy users manage categories, create events or upload materials ("submission" privileges on a contribution/event). This should already be the case in a properly-configured setup when it comes to category/event management. Note that a conference doing a Call for Abstracts actively invites external speakers (who the organizers may not know and thus cannot fully trust) to submit content, hence the need to update to a a fixed version ASAP in particular when using such workflows. |
Affected by 8 other vulnerabilities. |
|
VCID-nzny-2gtr-9yby
Aliases: CVE-2026-25738 GHSA-f47c-3c5w-v7p4 |
Indico has Server-Side Request Forgery (SSRF) in multiple places Indico makes outgoing requests to user-provides URLs in various places. This is mostly intentional and part of Indico's functionality, but of course it is never intended to let you access "special" targets such as localhost or cloud metadata endpoints. |
Affected by 2 other vulnerabilities. |
|
VCID-px34-3ut4-cyeu
Aliases: CVE-2026-33046 GHSA-rm2q-f7jv-3cfp |
Indico discloses local files resulting in Remote Code Execution through LaTeX injection > [!NOTE] > If server-side LaTeX rendering is not in use (ie `XELATEX_PATH` was not set in `indico.conf`), this vulnerability does not apply. ### Impact Due to vulnerabilities in TeXLive and obscure LaTeX syntax that allowed circumventing Indico's LaTeX sanitizer, it is possible to use specially-crafted LaTeX snippets which can read local files or execute code with the privileges of the user running Indico on the server. ### Patches It is recommended to update to [Indico 3.3.12](https://github.com/indico/indico/releases/tag/v3.3.12) as soon as possible. See [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update. It is also strongly recommended to enable the containerized LaTeX renderer (using `podman`), which isolates it from the rest of the system. See [the docs](https://docs.getindico.io/en/stable/installation/upgrade/#upgrading-to-3-3-12) for details - it is very easy and from now on the only recommended/supported way of using LaTeX. ### Workarounds Remove the `XELATEX_PATH` setting from `indico.conf` (or comment it out or set it to `None`) and restart the `indico-uwsgi` and `indico-celery` services to disable LaTeX functionality. ### For more information For any questions or comments about this advisory: - Open a thread in [the forum](https://talk.getindico.io/) - Send an email to [indico-team@cern.ch](mailto:indico-team@cern.ch) |
Affected by 0 other vulnerabilities. |
|
VCID-rdjk-wdan-aucm
Aliases: CVE-2026-28352 GHSA-rfpp-2hgm-gp5v |
Indico has a missing access check in the event series management API The API endpoint used to manage event series is missing an access check, allowing unauthenticated/unauthorized access to this endpoint. The impact of this is limited to: - Getting the metadata (title, category chain, start/end date) for events in an existing series - Deleting an existing event series: This just removes the series metadata, ie (if enabled) the links between events in the same series and the lecture series number in the event title - Modifying an existing event series: Just like for deleting, it would only allow to toggle the metadata display. It could also be used to set an event title pattern for the series, but this is only used when cloning an event from that series. That this vulnerability does NOT allow unauthorized access to events (beyond the basic metadata mentioned above), nor any kind of tampering with user-visible data in events. |
Affected by 1 other vulnerability. |
|
VCID-u63h-ajt2-tbft
Aliases: CVE-2021-30185 GHSA-wgpj-7c2j-vfjm PYSEC-2021-18 |
CERN Indico before 2.3.4 can use an attacker-supplied Host header in a password reset link. |
Affected by 9 other vulnerabilities. |
|
VCID-yduc-fh4z-3ueu
Aliases: CVE-2025-59035 GHSA-7cf7-9wrr-vrf4 |
Indico vulnerable to Cross-Site Scripting via LaTeX math code There is a Cross-Site-Scripting vulnerability when rendering LaTeX math code in contribution or abstract descriptions. |
Affected by 4 other vulnerabilities. |
|
VCID-z8zh-5u9q-d7hx
Aliases: CVE-2026-25739 GHSA-jxc4-54g3-j7vp |
Indico Affected by Cross-Site-Scripting via material uploads There is a Cross-Site-Scripting vulnerability when uploading certain file types as materials. |
Affected by 2 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||