# CVE-2026-133169: modified eCommerce Shopsoftware through 3.3.0 Stored XSS via products_model Field


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-3v6p-fqr9-45hm

## What is CVE-2026-133169?

CVE-2026-133169 is a medium-severity vulnerability in modified-shop, published on 19 Nov 2026. 

### Official description

modified eCommerce Shopsoftware through 3.3.0 contains a stored cross-site scripting vulnerability that allows authenticated administrators to inject scripts via the unsanitized products_model field. Attackers with product editing permission can store JavaScript that executes in browsers of other administrators, storefront visitors, and customers viewing carts and order history.

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

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

1 open source package ship an affected version, including modified-shop/modified-shop.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `modified-shop/modified-shop` | GitHub | `pkg:github/modified-shop/modified-shop` | All versions to 3.3.0 | None |

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

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

## Is CVE-2026-133169 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133169 is a medium-severity vulnerability in modified-shop, published on 19 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-133169 exists.

Affected packages and fixed versions:
- modified-shop/modified-shop (GitHub): affected all versions up to 3.3.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-133169/ (Markdown: https://insights.sbomify.com/CVE-2026-133169/index.md)
```

## Sources

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

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