VU#385711: PrestaShop Performance Debug Configuration Contains a PHP Code Injection Vulnerability
Source CERT/CC
Not known to be exploited : upgrade to 9.2.1 soon.
Data as of 9 Nov 2026, 15:04 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 9.2.1
Exploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade PrestaShop to 9.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PrestaShopPrestaShop | Affected
| Fixed in
|
AI-suggested
PrestaShop version 9.2.1 contains a fix for this vulnerability; administrators should upgrade affected installations to this version or later. If immediate upgrade is not possible, restrict debug mode configuration permissions to trusted administrators only and limit network access to the back office. Additionally, prevent the PHP process from having write permissions to config/defines.inc.php and config/defines_custom.inc.php where feasible, though this may impact legitimate configuration changes.
Description
PrestaShop's back-office Performance Debug mode contains a PHP code injection vulnerability. An authenticated user with permission to modify debug mode settings can inject arbitrary PHP code via crafted cookie configuration values, which are written into an executable PHP configuration file. This code executes with the privileges of the PHP process on subsequent requests. The vulnerability requires an authenticated back-office account with appropriate permissions and a writable configuration file. PrestaShop version 9.2.1 fixes this issue.