CVE-2026-45622

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 first upload a text file and rename it to .htaccess to inject Apache directives that register PHP-executable MIME types, then upload another file and rename it to .php to execute arbitrary operating system commands as the www-data user.

Vvveb is a powerful and easy to use content management system (CMS) that had a vulnerability in the checkout endpoint prior to version 1.0.8.3. It allowed logged-in attackers to reuse another user's cart data in their own checkout session.

Vvveb is a powerful and easy to use content management system (CMS) that prior to version 1.0.8.3 allowed an authenticated administrator to load another administrator's API token list by supplying that user's admin_id. This can disclose sensitive API tokens belonging to other administrators.

In Vvveb CMS prior to version 1.0.8.3, there is an SQL injection issue in the user order history page. An authenticated user can exploit URL parameters to manipulate SQL queries.

Vvveb CMS prior to version 1.0.8.2 does not validate the sign of the quantity parameter on the cart-add endpoint. Submitting a negative integer was accepted by the server, leading to negative values in order calculations.

Vvveb CMS before 1.0.8.1 contains a stored XSS vulnerability in the comment submission flow. The author field is submitted by an unauthenticated user on any public post page, stored without sanitization, and later rendered unsanitized in two distinct sinks.

Vvveb CMS version 1.0.8.2 contains a remote code execution vulnerability in its media upload handler that allows authenticated attackers to execute arbitrary operating system commands by uploading a PHP webshell with a .phtml extension.