Skip to main content
Menu
CVEs

CVE

prestashop/prestashop remote code execution via back-office theme import

CVE-2026-129957EUVD-2026-126414GHSA-8695-G229-836P

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

8.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 8.2.9, 9.2.1
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. PrestaShop 8.x before 8.2.9, or 9.x before 9.2.1 The attacker holds a back-office employee account that is allowed to import themes or modules

Published
Last modified
Reference
Last checked
28/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

PrestaShop has a path traversal flaw in the back-office theme and module archive import that lets a logged-in employee write files outside their intended directories. Reached over the network with high-level login, an attacker can place PHP files in web-accessible locations and run code on the server.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

PrestaShop before 8.2.9 and 9.0.0 before 9.2.1 contains a path traversal vulnerability in back-office theme and module archive import that allows authenticated employees to write files outside intended directories. Attackers can craft a theme name in config/theme.yml or upload a module archive extracted before validation to place PHP files in web-accessible locations and execute code.

Who should check

Teams running PrestaShop before 8.2.9 or 9.0.0 to before 9.2.1 that let back-office staff import themes or modules

“PrestaShop before 8.2.9 and 9.0.0 before 9.2.1”

vulncheck.com

cve.now Index

28Pcve.now Index 28 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Packagist packages
  • Severity9.6/10CVSS 8.6, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 35 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    PrestaShop 8.x before 8.2.9, or 9.x before 9.2.1 The attacker holds a back-office employee account that is allowed to import themes or modules
  • Upgrade to a fixed version: 8.2.9, 9.2.1.

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-129957 (PrestaShop before 8.2.9 and 9.2.1 Path Traversal RCE via Theme/Module Import), 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-129957 (entry last updated 2026-11-16):
Affected:
- Packagist package prestashop/prestashop: fixed in 8.2.9; from 9.0.0, fixed in 9.2.1
Fixed versions: 8.2.9, 9.2.1.
Conditions (all must be true for the bug to be hit):
- PrestaShop 8.x before 8.2.9, or 9.x before 9.2.1 (source: https://www.vulncheck.com/advisories/prestashop-before-8.2.9-and-9.2.1-path-traversal-rce-via-theme-module-import)
- The attacker holds a back-office employee account that is allowed to import themes or modules (source: https://github.com/PrestaShop/PrestaShop/security/advisories/GHSA-7q68-ch46-pxmc)
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-129957 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129957 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/PrestaShop/PrestaShop/security/advisories/GHSA-7q68-ch46-pxmc
- https://github.com/PrestaShop/PrestaShop/commit/446da0c02b8ad9bcbdd61f5791d8e551dfab1150
- https://github.com/PrestaShop/PrestaShop/commit/c1087264a329cdafb34b1ddbb368972043fd696e
- https://github.com/PrestaShop/PrestaShop/commit/63ffaf0a1c48638970e12a4d1c23d7272db6b84f
- https://github.com/PrestaShop/PrestaShop/commit/ff100164be70b573c9beb059fc828189e934479c
- https://github.com/PrestaShop/PrestaShop/releases/tag/9.2.1
- https://github.com/PrestaShop/PrestaShop/releases/tag/8.2.9
- https://github.com/PrestaShop/PrestaShop/blob/9.1.5/src/Core/Addon/Theme/ThemeManager.php#L404-L470
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-129957
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-129957"}.

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

Affected versions

Evidence 12

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 9

  1. Patch
  2. Patch
  3. Patch
  4. Patch
  5. Repository
  6. Repository
  7. Repository
  8. Repository
  9. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129957

Is CVE-2026-129957 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?

A back-office employee who is allowed to import themes or modules can write files outside the folder the import is meant to use. Writing files this way can lead to remote code execution on the store server.Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-129957?

prestashop/prestashop (Packagist): before 8.2.9; from 9.0.0 before 9.2.1.Source: cve.now feed data

Am I affected, and how do I check?

PrestaShop 8.x before 8.2.9 and PrestaShop 9.x before 9.2.1 are affected, but only when the employee account is allowed to import themes or modules. To check, look at the version shown in the back office or the install files, and check which employee profiles have theme or module import permission.Source: vulncheck.com, github.com

How do I fix CVE-2026-129957?

Upgrade to PrestaShop 8.2.9 or 9.2.1, depending on which branch the store runs. No vendor patch ids are given in the facts.Source: vulncheck.com, github.com