# CVE-2026-72576: Bludit - Stored Cross-Site Scripting via Malicious SVG Logo Upload

> An authenticated Author can inject arbitrary JavaScript via a malicious SVG logo, leading to stored XSS affecting other users.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-jvgc-4pc6-8x5f

## What is CVE-2026-72576?

CVE-2026-72576 is a medium-severity cross-site scripting vulnerability in Bludit, published on 10 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored cross-site scripting (XSS) vulnerability in Bludit 4.0.0-beta allows a low-privileged authenticated user (Author role) to inject arbitrary JavaScript by uploading a crafted SVG file as the site logo. A stored script tag in the SVG executes in the browser of any user who loads the logo.

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

## Which versions are affected by CVE-2026-72576?


## How do I fix CVE-2026-72576?

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

## Is CVE-2026-72576 being exploited?

There is no known exploitation of CVE-2026-72576 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72576 and fix it if it is affected.

What it is: CVE-2026-72576 is a medium-severity cross-site scripting vulnerability in Bludit, published on 10 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-72576 in the wild and no public exploit code.

Affected product: Bludit. 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-2026-72576/ (Markdown: https://insights.sbomify.com/CVE-2026-72576/index.md)
```

## Sources

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

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