CyberRota Analysis
AI-GeneratedThe vulnerability affects the oEmbedProxy() handler in Vvveb CMS versions prior to 1.0.8.5, allowing authenticated users with editor permissions to exploit an insecure URL validation mechanism. By manipulating the URL parameter, attackers can trigger the server to make unauthorized HTTP requests, potentially exposing sensitive internal service responses or cloud instance metadata. Organizations using Vvveb CMS should prioritize patching to version 1.0.8.5 to mitigate the risk of data leakage and unauthorized access.
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.5, the oEmbedProxy() handler in admin/controller/editor/editor.php accepts an attacker-controlled url parameter and passes it to getUrl(), while validateUrl() in system/functions.php checks only the hostname string and does not validate its resolved addresses. An authenticated admin-panel user with editor/* permission can invoke GET /admin/index.php?module=editor/editor&action=oEmbedProxy with a dotted hostname or normalized loopback form that resolves to a private, loopback, link-local, or reserved address, causing the server to issue an HTTP or HTTPS request and return the response body. Storefront users and anonymous visitors cannot invoke the endpoint, but no CSRF token is required because the action uses GET. This can disclose internal service responses or cloud instance metadata and associated credentials. This issue is fixed in version 1.0.8.5.