Skip to main content

Vvveb CMS CVE-2026-45622

| EUVDEUVD-2026-30583 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-05-15 GitHub_M
5.3
CVSS 4.0 · GitHub Advisory
Share

Severity by source

GitHub Advisory PRIMARY
5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
P
Scope
X

Lifecycle Timeline

3
Patch available
May 15, 2026 - 20:02 EUVD
Analysis Generated
May 15, 2026 - 19:37 vuln.today
CVSS changed
May 15, 2026 - 19:22 NVD
5.3 (MEDIUM)

DescriptionGitHub Advisory

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.

AnalysisAI

Unauthenticated reflected cross-site scripting (XSS) in Vvveb CMS versions prior to 1.0.8.3 enables attackers to execute arbitrary JavaScript in victim browsers via the public product return form. The customer_order_id parameter is reflected without sanitization in error messages when order lookups fail, allowing HTML injection. No public exploit identified at time of analysis. While CVSS 5.3 indicates moderate severity, the unauthenticated attack vector (PR:N) and low complexity (AC:L) make this readily exploitable against any site visitor, though user interaction (UI:P) is required to submit the malicious form.

Technical ContextAI

The vulnerability exists in Vvveb CMS's customer-facing order return functionality, specifically in the error handling logic for failed order lookups. When a user submits the product return form with an invalid order ID, the application constructs an error message by directly concatenating the user-supplied customer_order_id POST parameter into the string 'Order %s not found!' without HTML entity encoding or output escaping. This templated error message is then rendered in the frontend view, allowing injection of arbitrary HTML tags and JavaScript event handlers. This is a classic reflected XSS vulnerability (CWE-79) where untrusted input flows directly to a web page output context without proper sanitization. The affected component appears to be a publicly accessible feature requiring no authentication, making it a broad attack surface. Vvveb CMS is built on PHP and uses a templating system that failed to apply output encoding in this specific error path.

RemediationAI

Upgrade to Vvveb CMS version 1.0.8.3 or later, which contains the fix for this reflected XSS vulnerability. Download the patched version from the official Vvveb GitHub repository and follow standard CMS upgrade procedures including database backup and file replacement. Review the security advisory at https://github.com/givanz/Vvveb/security/advisories/GHSA-3xwm-8f6m-cfc6 for additional upgrade guidance. If immediate patching is not feasible, implement compensating controls: deploy a web application firewall (WAF) with XSS detection rules targeting the customer_order_id parameter in POST requests to the return form endpoint, though this may cause false positives requiring tuning. Additionally, implement Content Security Policy (CSP) headers with script-src 'self' to limit inline JavaScript execution, noting this may break legitimate dynamic features and requires testing. Review application logs for suspicious patterns in customer_order_id submissions containing script tags or event handlers as potential exploitation indicators. These workarounds reduce but do not eliminate risk, making upgrade the definitive solution.

More in Vvveb

View all
CVE-2025-44022 CRITICAL POC
9.8 May 12

An issue in vvveb CMS v.1.0.6 allows a remote attacker to execute arbitrary code via the Plugin mechanism. Rated critica

CVE-2025-8518 LOW POC
2.0 Aug 04

A vulnerability was found in givanz Vvveb 1.0.5. Rated medium severity (CVSS 5.1), this vulnerability is remotely exploi

CVE-2024-29272 MEDIUM POC
6.5 Mar 22

Arbitrary File Upload vulnerability in VvvebJs before version 1.7.5, allows unauthenticated remote attackers to execute

CVE-2024-29271 MEDIUM POC
6.1 Mar 22

Reflected Cross-Site Scripting (XSS) vulnerability in VvvebJs before version 1.7.7, allows remote attackers to execute a

CVE-2025-11028 MEDIUM POC
5.5 Sep 26

A security flaw has been discovered in givanz Vvveb up to 1.0.7.2. Rated medium severity (CVSS 5.5), this vulnerability

CVE-2025-9728 MEDIUM POC
5.3 Aug 31

A security vulnerability has been detected in givanz Vvveb 1.0.7.2. Rated medium severity (CVSS 5.3), this vulnerability

CVE-2026-6257 CRITICAL
9.2 Apr 20

Remote code execution in Vvveb CMS v1.0.8 allows authenticated administrators to execute arbitrary system commands as ww

CVE-2026-39918 CRITICAL
9.2 Apr 20

Remote code execution in Vvveb CMS versions prior to 1.0.8.1 allows unauthenticated attackers to inject arbitrary PHP co

CVE-2026-41930 CRITICAL
9.2 May 06

Hard-coded credentials in Vvveb's Docker deployment expose the entire application database to unauthenticated remote att

CVE-2026-34429 MEDIUM POC
5.1 Apr 20

Stored cross-site scripting in Vvveb prior to 1.0.8.1 allows authenticated users with media upload and rename permission

CVE-2026-49228 HIGH
8.8 Aug 18

Insecure Direct Object Reference in Vvveb CMS prior to 1.0.8.4 allows any authenticated low-privileged Vendor to read, d

CVE-2026-49221 HIGH
8.8 Aug 18

Broken object-level authorization in Vvveb CMS prior to 1.0.8.4 allows an authenticated low-privilege Vendor to access,

Share

CVE-2026-45622 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy