ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-whxq-pxj5-qq7v

SQL injection through back-office list filters

Published Aug 18, 2026 · catalog updated Aug 18, 2026 · SQL injection through back-office

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-whxq-pxj5-qq7v. A missing EPSS score is not a low risk. Compare SQL injection through back-office with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (SQL injection through back-office).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
composer prestashop/prestashop

### Impact This is an SQL injection issue in the back office. The filter names used by back-office listings were not sufficiently validated before being used to build the corresponding database query. By sending a crafted filter name, a logged-in employee could make the shop run a query of their own choosing. That allowed reading data from anywhere in the shop database, well beyond what their profile permits, including employee password hashes and the full customer and order tables. The reporter demonstrated it with the most restricted built-in profile, so the permission system did not contain the problem. ### Patches Upgrade to **PrestaShop 9.1.5** or **PrestaShop 8.2.8** The flawed code belongs to the legacy back-office controller and is also present in 1.7.x and earlier, which are end of life and will not receive a patch. ### Workarounds None ### References - [CWE-89: Improper Neutralization of Special Elements used in an SQL Command](https://cwe.mitre.org/data/definitions/89.html) - [OWASP: SQL Injection Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.html) - Report a security issue: security-core@prestashop.com --- _Credits: this vulnerability was discovered by **Claude (Anthropic)** as part of Anthropic's Coordinated Vulnerability Disclosure programme, verified by **Doyensec**, and responsibly reported to the PrestaShop security team by **Savio (Doyensec)**. We thank them for their report and for coordinating the disclosure with us.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • composer prestashop/prestashop>= 8.0.0, < 8.2.8
  • composer prestashop/prestashop>= 9.0.0, < 9.1.5

How to fix GHSA-whxq-pxj5-qq7v

  • Upgrade

    GHSA-whxq-pxj5-qq7v lists a fix boundary at 8.2.8. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 8.2.8

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-whxq-pxj5-qq7v. A missing EPSS score is not a low risk. Compare SQL injection through back-office with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with >= 8.0.0, < 8.2.8, >= 9.0.0, < 9.1.5. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

PrestaShop security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 18, 2026 · Maintainer security tabs

    Detected

    ### Impact This is an SQL injection issue in the back office. The filter names used by back-office listings were not sufficiently validated before being used to build the corresponding database query. By sending a crafted filter name, a logged-in employee could make the shop run a query of their own choosing. That allowed reading data from anywhere in the shop database, well beyond what their prof

Sources

  • Maintainer security tabsVendor advisoryGHSA-whxq-pxj5-qq7v

    ### Impact This is an SQL injection issue in the back office. The filter names used by back-office listings were not sufficiently validated before being used to build the corresponding database query. By sending a crafted filter name, a logged-in employee could make the shop run a query of their own choosing. That allowed reading data from anywhere in the shop database, well beyond what their prof

    github.com

Freshness

Last verified in this catalog Aug 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 1, 2026