# CVE-2025-12203: givanz Vvveb Code Editor functions.php sanitizeFileName path traversal

> Remote attackers can exploit a path traversal flaw in the Code Editor to read or modify arbitrary files on the server.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-cfvm-7f4p-fg84

## What is CVE-2025-12203?

CVE-2025-12203 is a medium-severity path traversal vulnerability in givanz Vvveb, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in givanz Vvveb up to 1.0.7.3. This issue affects the function sanitizeFileName of the file system/functions.php of the component Code Editor. Executing a manipulation of the argument File can lead to path traversal. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. This patch is called b0fa7ff74a3539c6d37000db152caad572e4c39b. Applying a patch is advised to resolve this issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Vvveb Vvveb.

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

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

## Is CVE-2025-12203 being exploited?

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

## Other vulnerabilities in givanz Vvveb

- [CVE-2025-44022](https://insights.sbomify.com/CVE-2025-44022/): Code injection in n/a (critical 9.8)
- [CVE-2025-11028](https://insights.sbomify.com/CVE-2025-11028/): givanz Vvveb Image information disclosure (medium 6.9)
- [CVE-2025-11029](https://insights.sbomify.com/CVE-2025-11029/): givanz Vvveb cross-site request forgery (medium 5.3)
- [CVE-2025-9728](https://insights.sbomify.com/CVE-2025-9728/): givanz Vvveb login.tpl cross site scripting (medium 5.3)
- [CVE-2025-9397](https://insights.sbomify.com/CVE-2025-9397/): givanz Vvveb media.php unrestricted upload (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12203 is a medium-severity path traversal vulnerability in givanz Vvveb, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12203 exists.

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

## Sources

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

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