---
id: CVE-2026-54507
title: >-
  Vvveb is a powerful and easy to use CMS with page builder to build websites,
  blogs or ecommerce stores
summary: >-
  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 pa…
severity: high
cvss: 8.4
cvssVector: 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N'
cwe:
  - CWE-918
vendor: givanz
product: Vvveb
affected:
  - Vvveb < 1.0.8.5
published: '2026-09-17'
updated: '2026-09-18'
sourceUpdated: '2026-09-18T15:17:09.047'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-54507'
references:
  - url: >-
      https://github.com/givanz/Vvveb/commit/bd280f5ce136f6da22c873fb1eea9cad8741e623
    label: security-advisories@github.com
  - url: 'https://github.com/givanz/Vvveb/releases/tag/1.0.8.5'
    label: security-advisories@github.com
  - url: 'https://github.com/givanz/Vvveb/security/advisories/GHSA-xxp7-59p2-4jr8'
    label: security-advisories@github.com
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-18T14:36:53.498947Z'
cvssSource: cna
epss: 0.0045
epssPercentile: 0.36362
ingestedAt: '2026-09-17T22:30:21.400Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.