CVE-2026-126372 in Vvveb
Summary
by MITRE • 11/13/2026
Vvveb through 1.0.8.6 contains an incomplete fix for CVE-2026-41934 that allows authenticated editor or site_admin users to write server-side templates by bypassing save restrictions. Attackers can upload or rename .tpl files via editor/code upload and rename actions, or evade isExecutableFile checks in save(), to inject PHP code into templates.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/13/2026
The vulnerability identified as CVE-2026-41934 represents a critical security flaw within Vvveb CMS versions up through 1.0.8.6, characterized by an incomplete remediation of a previously disclosed issue. This defect specifically impacts authenticated users holding editor or site_admin privileges, allowing them to bypass intended save restrictions and write server-side templates directly on the underlying file system. The core technical failure lies in the application's handling of template files during upload and rename operations. Although security measures were implemented to prevent the execution of malicious scripts, these controls are insufficient because they fail to adequately restrict the creation or modification of .tpl files that can be interpreted by the server as executable code.
The operational mechanism of this exploit involves attackers leveraging the editor's code upload functionality or utilizing file rename actions to inject PHP code into template files. The application attempts to mitigate risk through an isExecutableFile check within its save method, but this validation logic contains a bypass vector that allows malicious payloads to persist on the server. By uploading or renaming files with .tpl extensions containing embedded PHP scripts, attackers can effectively achieve remote code execution capabilities under the context of the web server process. This type of flaw aligns closely with CWE-94 Improper Control of Generation of Code (Code Injection), as it involves the injection of executable code into a template that is subsequently processed by the application environment.
From an offensive security perspective, this vulnerability maps to MITRE ATT&CK techniques related to Server-Side Request Forgery and Web Shell Deployment, specifically T1505.003 Server Side Template Injection or T1505.002 Web Shell: ASPX. The ability for authenticated users to write arbitrary code significantly escalates the threat landscape from simple data manipulation to full system compromise. Once a web shell is established via these template files, attackers can execute commands, exfiltrate sensitive database contents, pivot to other internal systems, and maintain persistent access to the compromised infrastructure.
Mitigation strategies must prioritize immediate patching of Vvveb CMS to versions that fully address CVE-2026-41934 with a complete fix rather than partial restrictions. In environments where upgrading is not immediately feasible, administrators should enforce strict file upload policies by whitelisting allowed extensions and disabling the ability for non-super-admin users to modify template files directly through the web interface. Additionally, implementing server-side configurations that prevent the execution of PHP code within template directories can provide a layer of defense in depth. Regular auditing of uploaded files and monitoring for anomalous changes to .tpl files are essential operational practices to detect potential exploitation attempts early.