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 CSPENABLED = True in indico.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

Impact There is a Cross-Site-Scripting vulnerability in fields that allow entering custom URLs.

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 CSPENABLED = True in indico.conf - this is recommended regardless of updating. - Only let trustworthy users manage events or create content (including material uploads 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

Impact 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.

Patches Developers should to update to Indico 3.3.11 as soon as possible. See the docs for instructions on how to update.

Workarounds - Developers can configure their webserver to restrict access to the series management API endpoint

For more information If there are any questions or comments about this advisory:

- Open a thread in our forum - Email Indico privately at indico-team@cern.ch