High severity · published Sep 17, 2026
CVE-2026-54507
Vvveb oEmbedProxy vulnerable to server-side request forgery
8.4
CVSS
0.4%
EPSS
No
On KEV
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 39% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
VV
Vvveb · givanz
< 1.0.8.5 · source: vendor
Affected product
VV
Vvveb
givanz
More from Vvveb
9.8
CVE-2026-41930
Vvveb < 1.0.8.2 Hard-coded Credentials Information Disclosure via phpMyAdmin
9.8
CVE-2026-39918
Vvveb < 1.0.8.1 Code Injection via Installation Endpoint
9.8
CVE-2025-9397
givanz Vvveb media.php unrestricted upload
8.8
CVE-2026-54612
Vvveb: Authenticated editor path traversal to PHP file write/RCE via data-v-save-global
8.8
CVE-2026-49228
Vvveb product authorization bypass allows Vendors to read, duplicate, or delete other Vendors' products