CVE-2026-6257: Vvveb CMS · Unrestricted File Upload
Affects Vvveb CMSSource CVE Database V5
Not known to be exploited · CVSS 9.2 Critical : upgrade to 1.0.8.2 as a priority.
Data as of 30 Oct 2026, 12:04 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 9.2 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 9.1 |
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.8.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Vvveb CMS to 1.0.8.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| VvvebVvveb CMS | Affected
| Fixed in
|
GitHubgivanz/Vvvebpkg:github/givanz/VvvebOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict authenticated user permissions to prevent file uploads or renaming, and consider disabling or restricting the media management functionality. Implementing web server-level controls to block execution of uploaded files with dangerous extensions may also help mitigate risk.
Description
Vvveb CMS before 1.0.8.2 contains a remote code execution vulnerability in its media management functionality where a missing return statement in the file rename handler allows authenticated attackers to rename files to blocked extensions .php or .htaccess. Attackers can exploit this logic flaw by first uploading a text file and renaming it to .htaccess to inject Apache directives that register PHP-executable MIME types, then uploading another file and renaming it to .php to execute arbitrary operating system commands as the www-data user.