CVE-2026-45800
HighSummary
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.
Risk Assessment
An attacker could gain access to database data, potentially leading to the exposure of sensitive information or system compromise.
Recommendation
It is recommended to update Vvveb CMS to version 1.0.8.3 or later to mitigate this vulnerability.
Other vulnerabilities in Vvveb CMS
See all- CVE-2026-46408High
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.
- CVE-2026-46407High
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.
- CVE-2026-44826High
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.
- CVE-2026-6249High
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.
- CVE-2026-6257Critical
Vvveb CMS version 1.0.8.2 contains a remote code execution vulnerability in its media management functionality. A missing return statement in the file rename handler allows authenticated attackers to rename files to blocked extensions .php or .htaccess.
Original NVD description (English source)
Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.3, there is an authenticated SQL injection issue in the frontend user order history page in Vvveb CMS. A normal frontend user can log in and access /user/orders. The order_by and direction request parameters are accepted from the URL, propagated through the Orders component, and directly concatenated into the SQL ORDER BY clause in OrderSQL::getAll(). Because of this, attacker-controlled input reaches SQL structure without a whitelist or safe query construction step. This vulnerability is fixed in 1.0.8.3.