Quick answers
- Is CVE-2024-7760 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-7760 being exploited in the wild.
- How severe is CVE-2024-7760?
- Low severity, with a CVSS score of 3, published 7 July 2026.
- Which products and versions are affected?
- Aim 2.0.19 through 3.22.0; aim (PyPI) ECOSYSTEM:introduced=0,last_affected=3.22.0.
- Is there a fix for CVE-2024-7760?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2024-7760 attacked?
- It is attacked over the network.
- Am I affected by CVE-2024-7760?
- Check whether you run Aim or aim (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in Aim's tracking server due to overly permissive Cross-Origin Resource Sharing (CORS) settings that allow cross-origin requests from all origins (CWE-352). This CSRF weakness affects all endpoints of the tracking server and can be chained with other existing vulnerabilities such as remote code execution, denial of service, and arbitrary file read/write capabilities. The attack requires user interaction (the victim must visit an attacker-controlled page while logged into Aim) but can be executed over the network without authentication to the attacker. No specific patch information is provided in the advisory, though the issue has been tracked since version 2.0.19 through at least version 3.22.0.
Affected products
- Aim Aim 2.0.19 through 3.22.0
Identifiers
- CVE-2024-7760
- GHSA-38r9-3j52-h92v
- PYSEC-2026-1082
Timeline
- 2025-03-20: disclosed
- 2025-07-22: other: GitHub reviewed vulnerability