CyberRota Analysis
AI-GeneratedThe Vvveb CMS, prior to version 1.0.8.4, is vulnerable due to improper access controls in its backend product revision operations, allowing low-privileged vendors to access and manipulate revisions of products owned by other vendors. This flaw can lead to unauthorized reading of sensitive content, restoration of revisions over live products, or deletion of revision records, potentially compromising product integrity and audit trails. Organizations using Vvveb should prioritize upgrading to the latest version to mitigate these risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.4, Vvveb backend product revision operations allow a low-privileged Vendor to access revisions for products owned by another Vendor. The admin/controller/product/revisions.php route reuses admin/controller/content/revisions.php, while admin/sql/sqlite/product_content_revision.sql trusts caller-controlled product_id, language_id, and created_at values without applying the current admin_id to revision reads, restores, and deletes. An attacker can read historic product content, restore a revision over another Vendor's live product content, or delete revision records, exposing private copy, corrupting product pages, and removing audit history. This issue is fixed in version 1.0.8.4.