Skip to main content
Menu
CVEs

Modified Shop local file inclusion in content manager

Affects modified-shop 3.3.0 and earlier, where an administrator stores ../ sequences in the content manager file name. CVSS rates it 8.6 High; no vendor rating is given. No fixed version is listed.

CVE-2026-133246Published November 19, 2026, updated

8.6HighCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Specific setups only

Summary

The modified eCommerce Shopsoftware has a local file inclusion flaw that lets an attacker with administrator access include arbitrary files from the server, including PHP code hidden in uploaded content files or images, as the web server user. The attacker reaches it remotely over the network by storing ../ sequences in the content manager file name, and requests to shop_content.php then include that stored path.

Written by a model

Original description

modified eCommerce Shopsoftware through 3.3.0 contains a local file inclusion vulnerability that allows administrators to include arbitrary server files by storing ../ sequences in the content manager file name. Unauthenticated requests to shop_content.php then pass the stored path to include(), executing embedded PHP in uploaded content files or images as the web server user.

Who should check

Teams running the modified eCommerce Shopsoftware (modified-shop) 3.3.0 or earlier, including shop_content.php and the content manager

“modified eCommerce Shopsoftware through 3.3.0”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Product is modified-shop 3.3.0 or earlier An administrator stores ../ sequences in the content manager file name
  2. 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-133246 (modified eCommerce Shopsoftware through 3.3.0 Local File Inclusion via shop_content.php), 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-133246 (entry last updated 2026-11-19):
Affected:
- modified-shop modified-shop: through 3.3.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Product is modified-shop 3.3.0 or earlier (source: https://www.vulncheck.com/advisories/modified-ecommerce-shopsoftware-through-3.3.0-local-file-inclusion-via-shop-content-php)
- An administrator stores ../ sequences in the content manager file name (source: https://www.vulncheck.com/advisories/modified-ecommerce-shopsoftware-through-3.3.0-local-file-inclusion-via-shop-content-php)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-133246 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133246 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/3766
- https://github.com/modified-shop/modified-shop/commit/1fff2b4913c77b323e56b1148d6cdd67e8e30aae
- https://github.com/vinniboy021-blip/Advisory/blob/main/modified_shopsoftware-LFI-RCE-shop_content.md
- https://github.com/modified-shop/modified-shop/blob/v3.3.0/shop_content.php#L87-L101
- https://github.com/modified-shop/modified-shop/blob/v3.3.0/admin/content_manager.php#L164-L168
- https://github.com/modified-shop/modified-shop
- https://www.vulncheck.com/advisories/modified-ecommerce-shopsoftware-through-3.3.0-local-file-inclusion-via-shop-content-php
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-133246
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-133246"}.

Affected versions

cve.now Index

18Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.6/10CVSS 8.6, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

Timeline

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

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 9

Questions about CVE-2026-133246

Is CVE-2026-133246 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. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

An administrator can store ../ sequences in a content manager file name, which allows the shop's shop_content.php to include arbitrary server files. The advisory also describes executing embedded PHP in uploaded content files or images as the web server user.

Source: vulncheck.com

Which versions are affected by CVE-2026-133246?

modified-shop: through 3.3.0.

Source: cve.now feed data

Am I affected, and how do I check?

The listed range is modified-shop 3.3.0 and earlier, with no earlier starting point given. The setup involves an administrator storing ../ sequences in the content manager file name, so checking the installed shop version against that range is the way to see where a given install falls.

Source: vulncheck.com

How do I fix CVE-2026-133246?

The checked facts name no fixed version and no vendor patch ids, so no upgrade target can be given from them. The vendor's advisory should be checked for a fix.

Source: vulncheck.com

Why do the sources disagree?

The description says the issue can be reached without authentication, while the CVSS vector records privileges required as High (PR:H). The description's account and the vector's account of required privileges conflict.

Source: vulncheck.com

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