# CVE-2024-38521: Persistent Cross-Site Scripting (XSS) in hushline inbox

> Attackers can inject malicious scripts into the Hush Line inbox via stored XSS, potentially compromising user sessions or executing code.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4v8c-r6h2-fhh3

## What is CVE-2024-38521?

CVE-2024-38521 is a high-severity cross-site scripting vulnerability in scidsg hushline, published on 28 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Hush Line is a free and open-source, anonymous-tip-line-as-a-service for organizations or individuals. There is a stored XSS in the Inbox. The input is displayed using the `safe` Jinja2 attribute, and thus not sanitized upon display. This issue has been patched in version 0.1.0.

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

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

It affects 1 product.


Products: Hushline Hush Line.

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

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

## Is CVE-2024-38521 being exploited?

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

## Other vulnerabilities in scidsg hushline

- [CVE-2024-38522](https://insights.sbomify.com/CVE-2024-38522/): CSP bypass in Hush Line (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38521 is a high-severity cross-site scripting vulnerability in scidsg hushline, published on 28 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38521 exists.

Affected product: scidsg hushline. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-38521/ (Markdown: https://insights.sbomify.com/CVE-2024-38521/index.md)
```

## Sources

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

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