CVE-2026-129957
PrestaShop theme and module import path traversal allows code execution (CVE-2026-129957)
PrestaShop before 8.2.9 and 9.0.0 to before 9.2.1 has a path traversal flaw in back-office theme and module import. An authenticated high-privilege employee can place PHP files in web-accessible locations and execute code. Update to PrestaShop 8.2.9 or 9.2.1.
What happened
PrestaShop's back-office theme and module archive import does not sufficiently constrain the paths used when extracting uploaded content. By crafting a theme name in config/theme.yml or by supplying a module archive that is extracted before validation, an attacker can write PHP files outside the intended directories. If those files are placed in a web-accessible location, the attacker can execute code on the PrestaShop instance.
In CVSS v4 terms, the flaw is network-based, has low attack complexity and requires no additional user interaction. The attacker needs high privileges — an authenticated employee with sufficient back-office access — and successful exploitation affects confidentiality, integrity and availability of the vulnerable system. The CVE record assigns a score of 8.6, high, with no impact on subsequent systems.
There is no indication in the CVE record of exploitation in the wild or public disclosure. PrestaShop has published fixed releases in 8.2.9 and 9.2.1.
Who is affected
Affected versions are PrestaShop before 8.2.9 and PrestaShop 9.0.0 up to before 9.2.1. This covers installations on the 8.x and 9.0 through 9.2 branches. The issue is in the back office; any organisation that lets staff import themes or modules on an unpatched version should treat itself as in scope.
The fix is available in PrestaShop 8.2.9 and PrestaShop 9.2.1. No other product lines are named in the record.
What to do now
- Update to a fixed release: PrestaShop 8.2.9 if you are on 8.x, or PrestaShop 9.2.1 if you are on 9.0.0 through versions before 9.2.1. These releases contain the path traversal fix.
- No workaround has been published. While you schedule the update, restrict back-office access to the smallest number of trusted employees and remove theme/module import rights from accounts that do not need them. The flaw requires authenticated high-privilege access, so reducing that access narrows exposure until patching is complete.
- After updating, confirm that no unexpected PHP files remain in web-accessible directories outside the usual theme and module paths. Review any recent theme or module imports against planned changes.
How to detect it
Look for PHP files in web-accessible directories that do not correspond to a known theme or module. The flaw allows files to be written outside the intended directories, so an unexpected PHP file in a writable web path should be investigated. Check any recently imported themes or modules against known change windows.
Beyond the patch
This is not a broad internet-facing pre-auth flaw; it is an authenticated path that turns a compromised or malicious back-office account into full code execution on the store. That makes two things worth reviewing: whether the import feature and related permissions are hardened, and whether you know which PrestaShop versions you are running and how quickly you can adopt vendor fixes. Implementation & Assessment Services can test the access and input-handling controls that would find this class of path traversal before an update lands. Supply Chain Defense & Third-Party Risk helps track open-source components like PrestaShop and their patch cycles, so the next fixed release does not sit unapplied.
Affected and fixed versions
| Product | Affected | Fixed in |
|---|---|---|
| PrestaShop | – < 8.2.9 9.0.0 – < 9.2.1 | 8.2.9 9.2.1 |
References
Vendor advisory
Patch and release notes
- github.com/PrestaShop/PrestaShop/commit/446da0c02b8ad9bcbdd61f5791d8e551dfab1150
- github.com/PrestaShop/PrestaShop/commit/c1087264a329cdafb34b1ddbb368972043fd696e
- github.com/PrestaShop/PrestaShop/commit/63ffaf0a1c48638970e12a4d1c23d7272db6b84f
- github.com/PrestaShop/PrestaShop/commit/ff100164be70b573c9beb059fc828189e934479c
- PrestaShop 9.2.1 Release Notes
- PrestaShop 8.2.9 Release Notes