CVE-2026-112904: Vvveb: Path Traversal in nextRestore() and nextBackup()
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 DIRBACKUP 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Vvvebto a version that resolves this vulnerability.Patch aa29cb0
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated administrator can exploit it. The vulnerability is in backup-controller functions, so exposure depends on an administrator being able to access those functions.
What access does an attacker need, and what can they do?
The attacker needs administrator authentication and can supply a crafted file GET parameter. They can read arbitrary server files through nextRestore() and write SQL dump content to arbitrary locations through nextBackup().
Which versions are affected?
Vvveb version 1.0.8.6 and prior are affected. The issue is patched in commit aa29cb0.
How can I determine whether my deployment is vulnerable?
Check whether the deployed source includes commit aa29cb0. Vulnerable code passes the file GET parameter from nextRestore() or nextBackup() directly into a path under DIR_BACKUP without calling sanitizeFileName().