CVE-2026-6257 | givanz Vvveb 1.0.8 unrestricted upload (EUVD-2026-23942)

VDB-358352 · CVE-2026-6257 · EUVD-2026-23942 GIVANZ VVVEB 1.0.8 UNRESTRICTED UPLOAD HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.8 $0-$5k 6.12 Summaryinfo A vulnerability categorized as critical has been discovered in givanz Vvveb 1.0.8. Impacted is an unknown function. Such manipulation leads to unrestricted upload. This vulnerability is uniquely identified as CVE-2026-6257. The attack can be launched remotely. No exploit exists. Detailsinfo A vulnerability was found in givanz Vvveb 1.0.8. It has been rated as critical. Affected by this issue is an unknown functionality. The manipulation with an unknown input leads to a unrestricted upload vulnerability. Using CWE to declare the problem leads to CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. Impacted is confidentiality, integrity, and availability. CVE summarizes: Vvveb CMS v1.0.8 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. The weakness was disclosed by Mohammed El Ouardani as 6fb8eaa998265e33e8802cbc220d8859dbc144f2. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-6257 since 04/13/2026. The exploitation is known to be easy. The attack may be launched remotely. Additional levels of successful authentication are required for exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/20/2026). The MITRE ATT&CK project declares the attack technique as T1608.002. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-23942). Productinfo Vendor givanz Name Vvveb Version 1.0.8 Website Product: https://github.com/givanz/Vvveb/ CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 6.9 VulDB Meta Temp Score: 6.8 VulDB Base Score: 4.7 VulDB Temp Score: 4.6 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 9.1 CNA Vector (VulnCheck): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Unrestricted upload CWE: CWE-434 / CWE-284 / CWE-266 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/13/2026 CVE reserved 04/20/2026 +7 days Advisory disclosed 04/20/2026 +0 days VulDB entry created 04/20/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: 6fb8eaa998265e33e8802cbc220d8859dbc144f2 Researcher: Mohammed El Ouardani Status: Not defined CVE: CVE-2026-6257 (🔒) GCVE (CVE): GCVE-0-2026-6257 GCVE (VulDB): GCVE-100-358352 EUVD: 🔒 Entryinfo Created: 04/20/2026 21:49 Updated: 04/20/2026 23:33 Changes: 04/20/2026 21:49 (75), 04/20/2026 23:33 (1) Complete: 🔍 Cache ID: 99:BB0:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸