# CVE-2024-6578: Stored XSS in aimhubio/aim

> Attackers can inject malicious scripts into run logs that execute in victims' browsers via React's dangerouslySetInnerHTML, potentially leading to session hijacking.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-p9f2-jg9w-cx69, PYSEC-2026-1092

## What is CVE-2024-6578?

CVE-2024-6578 is a high-severity cross-site scripting vulnerability in aimhubio/aim, published on 29 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stored cross-site scripting (XSS) vulnerability exists in aimhubio/aim version 3.19.3. The vulnerability arises from the improper neutralization of input during web page generation, specifically in the logs-tab for runs. The terminal output logs are displayed using the `dangerouslySetInnerHTML` function in React, which is susceptible to XSS attacks. An attacker can exploit this vulnerability by injecting malicious scripts into the logs, which will be executed when a user views the logs-tab.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-6578?

3 open source packages ship an affected version, including aim. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aim` | PyPI | All versions to 3.19.3 | None |
| `aim` | PyPI | All versions to 3.19.3 | None |
| `aim` | PyPI | All versions to 3.19.3 | None |

Products: Aimstack Aim.

## How do I fix CVE-2024-6578?

No fix has been published for CVE-2024-6578 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6578 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6578 exists.

## Other vulnerabilities in aimhubio/aim

- [CVE-2024-6396](https://insights.sbomify.com/CVE-2024-6396/): Arbitrary File Overwrite and Data Exfiltration in aimhubio/aim (critical 9.8)
- [CVE-2024-2195](https://insights.sbomify.com/CVE-2024-2195/): Remote Code Execution in aimhubio/aim (critical 9.8)
- [CVE-2024-6829](https://insights.sbomify.com/CVE-2024-6829/): Arbitrary File Overwrite through tarfile-extraction in aimhubio/aim (critical 9.1)
- [CVE-2024-8769](https://insights.sbomify.com/CVE-2024-8769/): Arbitrary File Deletion via Relative Path Traversal in aimhubio/aim (critical 9.1)
- [CVE-2025-51464](https://insights.sbomify.com/CVE-2025-51464/): Aim vulnerable to Cross-site Scripting (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6578 and fix it if it is affected.

What it is: CVE-2024-6578 is a high-severity cross-site scripting vulnerability in aimhubio/aim, published on 29 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6578 exists.

Affected packages and fixed versions:
- aim (PyPI): affected all versions up to 3.19.3; no fix listed
- aim (PyPI): affected all versions up to 3.19.3; no fix listed
- aim (PyPI): affected all versions up to 3.19.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6578/ (Markdown: https://insights.sbomify.com/CVE-2024-6578/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6578
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6578
- OSV: https://osv.dev/vulnerability/CVE-2024-6578

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6578/
Summaries are generated and may contain mistakes; the official description above is the record.