CVE-2026-54507: CWE-918: Server-Side Request Forgery (SSRF) in givanz Vvveb
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.
AI Analysis
Technical Summary
The vulnerability in givanz Vvveb affects the oEmbedProxy() handler in admin/controller/editor/editor.php, which accepts a user-controlled URL parameter passed to getUrl(). The validateUrl() function only checks the hostname string but does not validate the resolved IP addresses, allowing an attacker with authenticated editor-level access to invoke the endpoint with hostnames resolving to private, loopback, link-local, or reserved IP addresses. This causes the server to issue HTTP or HTTPS requests to internal services and return the response body, potentially exposing sensitive internal data such as cloud instance metadata and credentials. The endpoint is accessible via a GET request without CSRF protection. The issue is resolved in version 1.0.8.5.
Potential Impact
An attacker with authenticated editor permissions can exploit this SSRF vulnerability to make the server perform HTTP(S) requests to internal or otherwise restricted network addresses. This can lead to disclosure of internal service responses and sensitive cloud instance metadata, including credentials. Storefront users and anonymous visitors cannot exploit this vulnerability. The vulnerability has a high severity score of 8.4 (CVSS 4.0) due to its potential to expose sensitive internal information.
Mitigation Recommendations
Upgrade to givanz Vvveb version 1.0.8.5 or later, where this SSRF vulnerability is fixed. Until the upgrade, restrict editor-level access to trusted users only. Note that the vulnerable endpoint uses GET requests without CSRF tokens, so additional access controls or request validation may be necessary as a temporary mitigation.
CVE-2026-54507: CWE-918: Server-Side Request Forgery (SSRF) in givanz Vvveb
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.
CVSS v4.0
Score 8.4high
Affected software
givanz
Vvveb
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in givanz Vvveb affects the oEmbedProxy() handler in admin/controller/editor/editor.php, which accepts a user-controlled URL parameter passed to getUrl(). The validateUrl() function only checks the hostname string but does not validate the resolved IP addresses, allowing an attacker with authenticated editor-level access to invoke the endpoint with hostnames resolving to private, loopback, link-local, or reserved IP addresses. This causes the server to issue HTTP or HTTPS requests to internal services and return the response body, potentially exposing sensitive internal data such as cloud instance metadata and credentials. The endpoint is accessible via a GET request without CSRF protection. The issue is resolved in version 1.0.8.5.
Potential Impact
An attacker with authenticated editor permissions can exploit this SSRF vulnerability to make the server perform HTTP(S) requests to internal or otherwise restricted network addresses. This can lead to disclosure of internal service responses and sensitive cloud instance metadata, including credentials. Storefront users and anonymous visitors cannot exploit this vulnerability. The vulnerability has a high severity score of 8.4 (CVSS 4.0) due to its potential to expose sensitive internal information.
Mitigation Recommendations
Upgrade to givanz Vvveb version 1.0.8.5 or later, where this SSRF vulnerability is fixed. Until the upgrade, restrict editor-level access to trusted users only. Note that the vulnerable endpoint uses GET requests without CSRF tokens, so additional access controls or request validation may be necessary as a temporary mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-15T18:01:15.512Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aac5fee55bf5e2cf5f75527
Added to database: 09/17/2026, 21:47:26 UTC
Last enriched: 09/17/2026, 22:01:37 UTC
Last updated: 09/18/2026, 03:36:04 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.