# CVE-2025-41084: Stored Cross-Site Scripting (XSS) in Sesame web application

> Attackers can inject malicious scripts via unsanitized SVG uploads, leading to code execution in victim browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA: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:** 20 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-ffgq-vm8w-4m65

## What is CVE-2025-41084?

CVE-2025-41084 is a medium-severity cross-site scripting vulnerability in Sesame, published on 20 Jan 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

Stored Cross-Site Scripting (XSS) vulnerability in Sesame web application, due to the fact that uploaded SVG images are not properly sanitized. This allows attackers to embed malicious scripts in SVG files by sending a POST request using the 'logo' parameter in '/api/v3/companies/<ID>/logo', which are then stored on the server and executed in the context of any user who accesses the compromised resource.

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

## Which versions are affected by CVE-2025-41084?


## How do I fix CVE-2025-41084?

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

## Is CVE-2025-41084 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41084 and fix it if it is affected.

What it is: CVE-2025-41084 is a medium-severity cross-site scripting vulnerability in Sesame, published on 20 Jan 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-2025-41084 in the wild and no public exploit code.

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

## Sources

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

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