CVE-2023-30839

The damage here is authorization that doesn't hold. A back-office user in PrestaShop — any account with console access, regardless of the granular rights an admin assigned them — can slip past the SQL filtering and write, update, or delete directly in the database. The permission model says they shouldn't touch those tables; the SQL layer lets them anyway. On a live storefront that means order records, customer data, and admin credentials are all in reach of an account meant to have far less power.

What gates this is having a back-office account at all, which is why it's a 9.9 rather than a clean 10 — but that gate is thinner than it sounds. Staff accounts, contractor logins, and low-tier roles are exactly the credentials that get phished or reused, and a compromised junior account normally caps out at whatever rights it was granted. This bug removes that cap: one weak login becomes full database control on an e-commerce platform holding payment and customer PII.

For us the useful question isn't whether PrestaShop is patched in general but which instances predate 8.0.4 or 1.7.8.9 and how many active back-office accounts each carries. A shop with dozens of dormant staff logins is a far bigger target than a single-admin store, so we rank by account surface, not just version, and treat stale back-office accounts as the real blast radius.