# CVE-2026-54612: Vvveb: Authenticated editor path traversal to PHP file write/RCE via data-v-save-global

> Authenticated editors can exploit path traversal in Vvveb CMS to write PHP files, leading to remote code execution and full application compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 18 Sep 2026
- **Also known as:** GHSA-c3v9-3xrq-pvqv

## What is CVE-2026-54612?

CVE-2026-54612 is a high-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. From 1.0.0 until 1.0.8.5, saveGlobalElements() in admin/controller/editor/global-trait.php concatenates the attacker-controlled file portion of data-v-save-global to the active theme directory before loadHTMLFile() and file_put_contents() operate on it. An authenticated user with the default Editor role and editor/* permission can submit crafted HTML to module=editor/editor&action=save and traverse to an existing writable PHP file outside the theme directory. If the target is web-accessible, editor-controlled PHP content executes in the web server context; a shipped public/vadmin/index.php entrypoint can be used as an execution trampoline rather than requiring a test-only file. This can permit persistent webshell placement and compromise application confidentiality, integrity, and availability. This issue is fixed in version 1.0.8.5.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-54612 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54612 is a high-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: There is no known exploitation of CVE-2026-54612 in the wild and no public exploit code.

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-54612/ (Markdown: https://insights.sbomify.com/CVE-2026-54612/index.md)
```

## Sources

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

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