EUVD-2026-28459Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/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 Vendor (VulnCheck) · only source for this CVE.
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
4DescriptionCVE.org
Vvveb before 1.0.8.2 contains an unauthenticated reflected cross-site scripting vulnerability in the visual editor preview renderer that allows attackers to execute arbitrary JavaScript by manipulating the r query parameter and _component_ajax POST parameter. Attackers can craft a malicious link or auto-submitted form that causes victims to execute attacker-controlled JavaScript in the context of the Vvveb origin, as the gating function isEditor() performs no session, role, or token verification and the view handler injects raw HTML POST body content without sanitization.
AnalysisAI
Unauthenticated reflected cross-site scripting (XSS) in Vvveb before 1.0.8.2 allows remote attackers to execute arbitrary JavaScript in the context of the Vvveb origin by manipulating the r query parameter and _component_ajax POST parameter in the visual editor preview renderer. The vulnerability exploits the absence of session, role, or token verification in the isEditor() gating function combined with unsanitized injection of POST body content, requiring only user interaction to trigger but affecting all versions prior to 1.0.8.2. Active exploitation status is not confirmed, but a vendor-released patch is available.
Technical ContextAI
Vvveb is a visual website builder and content management system that uses a client-side editor to preview and manipulate web pages. The vulnerability resides in the visual editor preview renderer component, which accepts user-controlled input via the r query parameter and _component_ajax POST parameter. The root cause (CWE-79: Improper Neutralization of Input During Web Page Generation) stems from two compounding failures: the isEditor() authentication gate performs no cryptographic verification (no session token, role-based access control, or CSRF tokens), and the view handler directly injects raw HTML from POST body content without HTML entity encoding, JavaScript escaping, or content security policy filtering. This allows an attacker to craft a malicious URL or auto-submitted form that, when visited by a Vvveb user, renders attacker-supplied JavaScript within the authenticated user's browser context, granting access to sensitive data, session tokens, and user actions on the Vvveb origin (CPE: cpe:2.3:a:givanz:vvveb:*:*:*:*:*:*:*:*).
RemediationAI
Upgrade immediately to Vvveb 1.0.8.2 or later to apply the vendor-released patch. The patched version addresses the vulnerability by implementing input sanitization in the view handler and strengthening the isEditor() authentication gate with proper session and token verification. If immediate upgrade is not feasible, apply the following compensating controls with noted trade-offs: (1) Disable or restrict access to the visual editor preview renderer endpoint for non-authenticated users by configuring web server rules to require authentication tokens for the r and _component_ajax parameters-this prevents unauthenticated exploitation but may break legitimate editor functionality for users with disabled JavaScript cookies or privacy-focused browser configurations. (2) Implement a Content-Security-Policy (CSP) header with script-src 'self' to prevent inline script execution-this mitigates XSS payload execution but may break inline editor scripts and require vendor CSP compatibility testing. (3) Use HTTP-only, SameSite=Strict cookies for session tokens to prevent attacker script from exfiltrating session data, though this does not prevent DOM manipulation or credential theft via keylogging. (4) Deploy a Web Application Firewall (WAF) rule to block requests containing HTML tags or JavaScript keywords in the r and _component_ajax parameters-this reduces false negatives but risks blocking legitimate use cases and requires ongoing rule tuning. Prioritize patching to version 1.0.8.2 over compensating controls, as these controls do not address the underlying authentication and sanitization flaws. See advisory: https://github.com/givanz/Vvveb/security/advisories/GHSA-wwmv-4g9g-p48g and commit: https://github.com/givanz/Vvveb/commit/54a9e846fb94192f1b31ae81d81d25c874662e6a.
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,
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today