🛡️ CVE-2025-53640 — indico
Description
Indico vulnerability allows attackers to bulk dump user details
Impact
An endpoint used to display details of users listed in certain fields (such as ACLs) could be misused to dump basic user details (such as name, affiliation and email) in bulk.
> [!TIP]
> If your instance allows everyone to create a user account, and you wish to truly restrict access to these user details, consider restricting user search to managers. You can find details on the newly introduced indico.conf setting [ALLOW_PUBLIC_USER_SEARCH](https://docs.getindico.io/en/stable/config/settings/#ALLOW_PUBLIC_USER_SEARCH) in our documentation.
Patches
You should to update to [Indico 3.3.7](https://github.com/indico/indico/releases/tag/v3.3.7) as soon as possible.
See [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update.
Workarounds
It is possible to restrict access to the affected endpoints (e.g. in the webserver config), but doing so would break certain form fields which could no longer show the details of the users listed in those fields, so upgrading instead is highly recommended.
For more information
If you have any questions or comments about this advisory:
- Open a thread in [our forum](https://talk.getindico.io/)
- Email us privately at [[email protected]](mailto:[email protected])
Credits
This vulnerability was identified during a security assessment conducted as part of the Red Team Residency Program at RNP (Rede Nacional de Ensino e Pesquisa).
The research and testing were performed by a security researcher working under RNP’s authorization and coordination.
Special acknowledgment goes to the RNP Security Team, which provided the infrastructure, methodology, and ethical oversight for this work.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. Rated impact: confidentiality low, integrity none, availability none.
Weakness class
CVE-2025-53640 is classified as CWE-200: Exposure of Sensitive Information. Information that should stay internal is disclosed to someone who is not authorised to see it.
Affected software
CVE-2025-53640 is recorded against 1 package.
- indico (from 2.2 up to 3.3.7)
Timeline and source
Published on 14 July 2025 and last revised on 7 July 2026. A public exploit is known to exist, which raises the urgency of patching considerably. Record sourced from OSV.
References
github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
docs.getindico.io (Web)
docs.getindico.io (Web)
github.com (Package)
github.com (Web)
www.vicarius.io (Web)
www.vicarius.io (Web)
Details
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| indico | 2.2 | 3.3.7 |
References
Similar Threats
- High CVE-2026-33046
- Medium CVE-2026-28352
- Medium CVE-2026-25738
- Medium CVE-2026-25739
- Medium CVE-2025-59034
More CVE 2025 advisories
Browse all of CVE 2025 in the advisory index.
Exploit Protection
Are you running indico?
CVE-2025-53640 carries CVSS 6.5 Medium rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.
Check My Site For CVE-2025-53640 →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.