# CVE-2025-40633: Stored Cross-Site Scripting (XSS) in Koibox

> An authenticated attacker can inject malicious JavaScript via profile picture uploads, potentially leading to session hijacking or 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 May 2025
- **Updated:** 20 May 2025
- **Also known as:** GHSA-xrqm-569v-qj6w

## What is CVE-2025-40633?

CVE-2025-40633 is a medium-severity cross-site scripting vulnerability in Koibox, published on 20 May 2025. 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 has been found in 
Koibox for versions prior to e8cbce2. This vulnerability allows an 
authenticated attacker to upload an image containing malicious 
JavaScript code as profile picture in the 
'/es/dashboard/clientes/ficha/' endpoint

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

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


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

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

## Is CVE-2025-40633 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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