# CVE-2026-112904: Vvveb: Path Traversal in nextRestore() and nextBackup()


- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-75qx-795q-v79g

## What is CVE-2026-112904?

CVE-2026-112904 is a high-severity vulnerability in givanz Vvveb, published on 23 Oct 2026. 

### Official description

Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. In versions 1.0.8.6 and prior, the nextRestore() and nextBackup() functions in the backup controller accept a file GET parameter and concatenate it directly to DIR_BACKUP without calling sanitizeFileName(). This allows an authenticated administrator to read arbitrary files on the server (via nextRestore) and write SQL dump content to arbitrary locations (via nextBackup). This is inconsistent with the sibling functions restore(), delete(), and download() which all correctly call sanitizeFileName() first. This issue has been patched via commit aa29cb0.

Weakness: CWE-26 (Path Traversal: '/dir/../filename')

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


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

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

## Is CVE-2026-112904 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112904 is a high-severity vulnerability in givanz Vvveb, published on 23 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112904 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-2026-112904/ (Markdown: https://insights.sbomify.com/CVE-2026-112904/index.md)
```

## Sources

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

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