PrestaShop Performance Debug Configuration PHP Code Injection
- Exploited
- No known exploitation
- Fix
- Fixed in 9.2.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 9.2.1.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
PrestaShop, the open-source e-commerce platform, contains a PHP code injection flaw in the back-office Performance debug-mode settings. A logged-in back-office user with permission to change debug settings can inject PHP code through the debug cookie name or value, which then runs with the privileges of the web-server process.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
PrestaShop contains an authenticated PHP code injection vulnerability in the back-office Performance debug-mode configuration. A back-office user with permission to modify debug settings can supply a crafted debug_cookie_name or debug_cookie_value that is written without sufficient escaping into a PHP configuration file. When PrestaShop subsequently loads the generated file, the injected PHP code is executed with the privileges of the web-server process.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.4/10CVSS 5.4, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 9.2.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- PrestaShop PrestaShop
From 1.5.0.0 · fixed in 9.2.1
Evidence 3
- Advisory
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124916
Is CVE-2026-124916 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
Which versions are affected by CVE-2026-124916?
PrestaShop: from 1.5.0.0 before 9.2.1.Source: cve.now feed data
How do I fix CVE-2026-124916?
Upgrade to a fixed version: 9.2.1.Source: cve.now feed data