What is the CVSS score of EUVD-2026-26406?

EUVD-2026-26406 has a CVSS 3.1 base score of 5.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Shopizer EUVD-2026-26406

| CVE-2026-36766 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-04-30 mitre

XSS N A

5.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.4 MEDIUM

AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Apr 30, 2026 - 20:30 vuln.today

CVSS changed

Apr 30, 2026 - 19:22 NVD

5.4 (MEDIUM)

EUVD ID Assigned

Apr 30, 2026 - 18:15 euvd

EUVD-2026-26406

Analysis Generated

Apr 30, 2026 - 18:15 vuln.today

CVE Published

Apr 30, 2026 - 00:00 nvd

MEDIUM 5.4

DescriptionCVE.org

Multiple authenticated cross-site scripting (XSS) vulnerabilities in the XssHttpServletRequestWrapper class of shopizer v3.2.5 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the getInputStream() or getReader() functions.

AnalysisAI

Authenticated cross-site scripting (XSS) vulnerabilities in Shopizer v3.2.5's XssHttpServletRequestWrapper class allow authenticated attackers to execute arbitrary web scripts or HTML by injecting crafted payloads into the getInputStream() or getReader() functions. The vulnerability requires user interaction (UI:R) and authenticated access (PR:L), limiting exploitation to logged-in users who can be socially engineered into clicking malicious links or submitting forms. No public exploit code or active exploitation has been confirmed at time of analysis.

Technical ContextAI

The vulnerability exists in the XssHttpServletRequestWrapper class, a security component designed to filter and sanitize HTTP request input. XssHttpServletRequestWrapper is a servlet wrapper that typically overrides request methods like getInputStream() and getReader() to intercept and clean request bodies before they reach application handlers. The flaw indicates that this wrapper's sanitization logic is insufficient when processing HTTP request streams, allowing specially crafted payloads to bypass XSS filters. CWE-79 (Improper Neutralization of Input During Web Page Generation) identifies the root cause: the application fails to properly encode or validate user-supplied data before rendering it in web contexts, enabling attackers to inject malicious scripts that execute in victims' browsers with the privileges of authenticated users.

RemediationAI

Upgrade Shopizer to the patched version addressing this vulnerability; consult the GitHub issues page (https://github.com/shopizer-ecommerce/shopizer/issues/1093) and project releases for the exact fixed version number, which is not provided in this analysis. Immediate compensating controls include: (1) Restrict access to the admin or authenticated user panel to a whitelist of trusted IP ranges or VPNs, reducing the attack surface to insider threats; note this may impact remote work. (2) Implement HTTP Content-Security-Policy (CSP) headers with script-src 'self' to prevent injected scripts from executing, even if payloads bypass the XssHttpServletRequestWrapper-this is compatible with most e-commerce functionality. (3) Enable HTML entity encoding in response templates to ensure any HTML/script tags rendered from request bodies are displayed as text, not executed. (4) Conduct code review of the XssHttpServletRequestWrapper class to verify that all output encoding functions (e.g., OWASP ESAPI encoders) are correctly applied to data from getInputStream() and getReader() before rendering. Patch application is the definitive fix and should be prioritized once released.