# CVE-2026-5615: givanz Vvvebjs File Upload Endpoint upload.php cross site scripting

> Attackers can inject malicious scripts via the file upload endpoint, potentially leading to code execution or security bypass in Vvvebjs.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 6 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-p873-9x3v-gmvh

## What is CVE-2026-5615?

CVE-2026-5615 is a medium-severity cross-site scripting vulnerability in givanz Vvvebjs, published on 6 Apr 2026. 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

A weakness has been identified in givanz Vvvebjs up to 2.0.5. The affected element is an unknown function of the file upload.php of the component File Upload Endpoint. This manipulation of the argument uploadAllowExtensions causes cross site scripting. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. Patch name: 8cac22cff99b8bc701c408aa8e887fa702755336. Applying a patch is the recommended action to fix this issue. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-5615 being exploited?

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

Public exploit code:

- CVE-2026-5615 (github_poc): https://github.com/sahmsec/CVE-2026-5615
- VvvebJs <= 2.0.5 - Cross-Site Scripting (nuclei): http/cves/2026/CVE-2026-5615.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5615 is a medium-severity cross-site scripting vulnerability in givanz Vvvebjs, published on 6 Apr 2026. 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-2026-5615 exists.

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

## Sources

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

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