1-minute read
What a defender needs to know
PrestaShop back-office accounts allowed to edit Performance > Debug mode can inject PHP through the debug-cookie settings, according to CERT/CC. The values of debug_cookie_name and debug_cookie_value are written into a define() statement in config/defines.inc.php or config/defines_custom.inc.php. PrestaShop loads the file on a later request, running injected statements with the PHP process’s privileges. An attacker needs both the configuration permission and a file the PHP process can write. CSRF protection does not stop someone who controls a permitted account.
The CVE Program record lists releases from 1.5.0.0 to below 9.2.1; CERT/CC says the affected range remains to be confirmed. Upgrade stores running earlier versions to 9.2.1 or later. Limit Debug mode editing to trusted administrators and restrict back-office network access. Compare the two named PHP files with approved deployment copies, paying attention to unexpected statements near the debug-cookie definitions. A PHP write restriction can help where maintenance allows it, but can block legitimate configuration changes.
Verify the installed release, role permissions and contents of both files after upgrading. Investigate unexplained PHP as a possible store compromise, preserving the diff and administrative change history before cleanup.