CVE-2024-2196: Aim Cross-Site Request Forgery vulnerability allows user to delete runs and perform other operations
aimhubio/aim is vulnerable to Cross-Site Request Forgery (CSRF), allowing attackers to perform actions such as deleting runs, updating data, and stealing data like log records and notes without the user's consent. The vulnerability stems from the lack of CSRF and CORS protection in the aim dashboard.
Published Apr 10, 2024
Affected packages
aim
- Ecosystem
- PyPI
- Affected
- <= 3.17.5
- Fixed in
- No patched version yet
- Check
pip show aim
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
aimhubio/aim is vulnerable to Cross-Site Request Forgery (CSRF), allowing attackers to perform actions such as deleting runs, updating data, and stealing data like log records and notes without the user's consent. The vulnerability stems from the lack of CSRF and CORS protection in the aim dashboard. An attacker can exploit this by tricking a user into executing a malicious script that sends unauthorized requests to the aim server, leading to potential data loss and unauthorized data manipulation.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2025-51464
Aim vulnerable to Cross-site Scripting
medium5.3No fixJul 22, 2025CVE-2025-5321
Aim Vulnerable to Sandbox Escape Leading to Remote Code Execution
low6.3No fixMay 29, 2025CVE-2024-10110
Aim Vulnerable to Denial of Service (DoS)
high7.5No fixMar 20, 2025CVE-2024-12777
Aim vulnerable to Synchronous Access of Remote Resource without Timeout
medium5.9No fixMar 20, 2025CVE-2024-12778
Aim Uncontrolled Resource Consumption vulnerability
high7.5No fixMar 20, 2025CVE-2024-6483
Aim Relative Path Traversal vulnerability
medium5.3No fixMar 20, 2025
