# CVE-2026-36766: Shopizer is vulnerable to Cross-site Scripting

> Authenticated attackers can execute arbitrary scripts in Shopizer via XSS in the XssHttpServletRequestWrapper class.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Apr 2026
- **Updated:** 30 Apr 2026
- **Also known as:** GHSA-fqcw-2xhj-p63g

## What is CVE-2026-36766?

CVE-2026-36766 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-36766?

2 open source packages ship an affected version, including com.shopizer:shopizer.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.shopizer:shopizer` | Maven | All versions to 2.16.0 | None |
| `com.shopizer:shopizer` | Maven | All versions to 2.16.0 | None |

## How do I fix CVE-2026-36766?

No fix has been published for CVE-2026-36766 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-36766 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36766 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-36766 and fix it if it is affected.

What it is: CVE-2026-36766 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36766 exists.

Affected packages and fixed versions:
- com.shopizer:shopizer (Maven): affected all versions up to 2.16.0; no fix listed
- com.shopizer:shopizer (Maven): affected all versions up to 2.16.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-36766/ (Markdown: https://insights.sbomify.com/CVE-2026-36766/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-36766
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-36766
- OSV: https://osv.dev/vulnerability/CVE-2026-36766

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-36766/
Summaries are generated and may contain mistakes; the official description above is the record.