CyberRota Analysis
AI-GeneratedThe Vvveb CMS prior to version 1.0.8.4 is vulnerable due to improper access controls in its backend post revision operations, allowing low-privileged users to access, restore, or delete revisions of posts owned by other authors. This can lead to unauthorized exposure of sensitive content, corruption of published posts, and loss of audit trails. Organizations using Vvveb should prioritize updating 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 post revision operations allow a low-privileged Author to access revisions for posts owned by another Author. The admin/controller/content/revisions.php controller and admin/sql/sqlite/post_content_revision.sql queries trust caller-controlled post_id, language_id, and created_at values without consistently applying the current admin_id to revision lists, reads, restores, and deletes. An attacker can read historic post content, restore a revision over another Author's live post content, or delete revision records, exposing drafts, corrupting published content, and removing audit history. This issue is fixed in version 1.0.8.4.