Skip to main content
Menu
CVEs

Modified Shop stored XSS in products_model field

CVE-2026-133169EUVD-2026-130210GHSA-3V6P-FQR9-45HMPublished November 19, 2026, updated

4.8MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

The modified eCommerce Shopsoftware contains a stored cross-site scripting flaw in its unsanitized products_model field. An attacker who has product editing rights can reach it over the network and save JavaScript that runs in the browsers of other administrators, storefront visitors, and customers when they view carts or order history, though a user must take an action for it to trigger.

Written by a model

Original 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.

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133169 (modified eCommerce Shopsoftware through 3.3.0 Stored XSS via products_model Field), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133169 (entry last updated 2026-11-19):
Affected:
- modified-shop modified-shop: through 3.3.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133169 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133169 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/modified-shop/modified-shop/pull/3748
- https://github.com/modified-shop/modified-shop/commit/a5b30815de21c55e2463e8469b6c565dc635cf86
- https://github.com/modified-shop/modified-shop/issues/3782
- https://github.com/capivara-research/modified-shop-xss-products-model
- https://github.com/modified-shop/modified-shop/blob/c531afbf7279f6e60ca7cda09f2c9d7ca5305c46/admin/listproducts.php#L68
- https://github.com/modified-shop/modified-shop
- https://www.vulncheck.com/advisories/modified-ecommerce-shopsoftware-through-3.3.0-stored-xss-via-products-model-field
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133169
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133169"}.

Affected versions

cve.now Index

23Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.8/10CVSS 4.8
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 9

Questions about CVE-2026-133169

Is CVE-2026-133169 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133169?

modified-shop: through 3.3.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.