# CVE-2026-54613: Vvveb: Path Traversal in Revision Backup Reader/Deleter via Unsanitized theme Parameter

> An authenticated editor can exploit unsanitized theme parameters to read or delete backup files outside the intended directory.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 17 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-gjxp-vrcw-69v8

## What is CVE-2026-54613?

CVE-2026-54613 is a medium-severity path traversal vulnerability in givanz Vvveb, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.5, getThemeFolder() in admin/controller/editor/revisions.php returns the attacker-controlled theme parameter without sanitization, and backupFolder() concatenates it beneath DIR_THEMES before editor/revisions/load or editor/revisions/delete operates on a named .html file. sanitizeBackupFileName() strips traversal characters only from the separate file parameter and does not protect the theme directory component. An authenticated user with the default Editor role and editor/* permission can submit traversal sequences that redirect file_get_contents() or unlink() to a reachable backup subdirectory outside the web root. A valid admin session and CSRF token are required, the read is limited to .html files in backup directories, and deletion additionally requires filesystem write permission. This can disclose sensitive exported site content or remove backup data. This issue is fixed in version 1.0.8.5.

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

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


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

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

## Is CVE-2026-54613 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54613 is a medium-severity path traversal vulnerability in givanz Vvveb, published on 17 Sep 2026. 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-2026-54613 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-54613/ (Markdown: https://insights.sbomify.com/CVE-2026-54613/index.md)
```

## Sources

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

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