CVE-2026-36766
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAuthenticated XSS vulnerabilities exist in the XssHttpServletRequestWrapper class of shopizer v3.2.5. The getInputStream() and getReader() functions fail to properly sanitize input, allowing attackers with valid authentication to inject malicious scripts or HTML through crafted payloads.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify shopizer installationLocate shopizer application files (check for shopizer WAR file, exploded directory, or source code). Look for pom.xml or build configuration files that specify the version.Affected if The application is running shopizer version 3.2.5 specifically.
-
Locate the vulnerable classFind the XssHttpServletRequestWrapper.java file within the project source code or decompiled classes. Search in the servlet or filter packages.Affected if The XssHttpServletRequestWrapper class exists and is present in the application.
-
Inspect getInputStream() methodOpen XssHttpServletRequestWrapper.java and examine the getInputStream() method implementation. Look for input sanitization, validation, or encoding logic.Affected if The getInputStream() method lacks proper input sanitization or encoding (no HTML entity encoding, no input validation, no sanitization library usage).
-
Inspect getReader() methodExamine the getReader() method in the same XssHttpServletRequestWrapper class for the same sanitization controls.Affected if The getReader() method similarly lacks proper input sanitization or encoding.
-
Check if wrapper is actively usedSearch configuration files (web.xml, Spring configurations) for filters or servlets that utilize XssHttpServletRequestWrapper. Verify if incoming HTTP requests are processed through this wrapper.Affected if The XssHttpServletRequestWrapper is configured as a request filter or wrapper, meaning user input flows through the unsanitized methods.
A user is affected if running shopizer version 3.2.5, the XssHttpServletRequestWrapper class is present with unsanitized getInputStream()/getReader() methods, and this wrapper is actively applied to process HTTP requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper input sanitization and output encoding in the XssHttpServletRequestWrapper class, specifically within the getInputStream() and getReader() methods to neutralize XSS attack vectors.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36766 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36766 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data