VYPR
Medium severityNVD Advisory· Published May 15, 2026· Updated May 18, 2026

CVE-2026-45622

CVE-2026-45622

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.3, there is an unauthenticated reflected cross-site scripting (XSS) issue in the public product return form in Vvveb CMS. The customer_order_id POST parameter is inserted into the Order %s not found! error message when the order lookup fails, and that message is rendered in the frontend template without HTML escaping. As a result, attacker-controlled HTML/JavaScript executes in the submitting user's browser. This vulnerability is fixed in 1.0.8.3.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

An unauthenticated reflected XSS in Vvveb CMS ≤1 CMS < 1.0.8.3 allows attackers to execute arbitrary JavaScript via the customer_order_id parameter in the public return form.

Vulnerability

Overview

CVE-2026-45622 is an unauthenticated reflected cross-site scripting (XSS) vulnerability in Vvveb CMS versions prior to 1.0.8.3. The flaw resides in the public product return form endpoint (/index.php?module=user/return-form&action=save). When a user submits the form with a non-existing order ID, the customer_order_id POST parameter is directly interpolated into the error message Order %s not found! via sprintf() in app/controller/user/return-form.php. This message is then rendered in the frontend template without HTML escaping, allowing attacker-controlled HTML/JavaScript to execute in the submitting user's browser [1].

Exploitation

The attack requires no authentication and can be triggered by any user who visits the public return form. An attacker crafts a malicious payload (e.g., ">) and submits it as the customer_order_id value along with valid form fields. When the order lookup fails, the server reflects the payload into the error message, and the browser executes the injected script. The attack is delivered via a POST request, which may require a CSRF require a CSRF token, but the advisory notes that arbitrary script execution still occurs in the browser context [1].

Impact

Successful exploitation results in arbitrary JavaScript execution in the context of the victim's session on the Vvveb CMS site. This can lead to session hijacking, defacement, or theft of sensitive information displayed on the page. The advisory does not claim does not include direct server compromise or privilege escalation, but the XSS can be used as a stepping stone for further attacks [1].

Mitigation

The vulnerability is fixed in Vvveb CMS version 1.0.8.3. Users should upgrade immediately. No workarounds are documented, but sanitizing the customer_order_id input or escaping output in the template would prevent exploitation [1].

AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

1

News mentions

0

No linked articles in our index yet.