Finding and attribution
Back-office listing filter names were insufficiently validated before being incorporated into database queries. A logged-in employee could submit a crafted filter name to read data outside their profile’s permissions, including employee password hashes and customer and order tables. The advisory states the reporter demonstrated the issue with the most restricted built-in profile.
Product: PrestaShop back-office listings. AI system: Claude (model/version not identified). Team / organization: Anthropic and Doyensec; PrestaShop maintainers.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): The primary PrestaShop advisory explicitly says Claude (Anthropic) discovered the vulnerability as part of Anthropic’s coordinated disclosure program; Doyensec verified it and reported it to the project.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The public advisory has GHSA-whxq-pxj5-qq7v but no CVE assigned. It rates the issue Moderate (CVSS 6.5); exploitation requires a logged-in employee. Older 1.7.x and earlier versions are stated to be end of life and unpatched.
Remediation status: fix documented. Upgrade supported installations to PrestaShop 9.1.5 or 8.2.8. No workaround is given. The same flawed legacy back-office controller is also present in 1.7.x and earlier, which the project says are end of life and will not be patched.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 18 Aug 2026. AI attribution dated 18 Aug 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: data disclosure.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Case-level evidence: data disclosure.
Prerequisites / affected scope: A logged-in employee crafts a back-office list filter; even the most restricted built-in profile can read arbitrary shop database data, including employee hashes, customer and order tables..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: Upgrade supported installations to PrestaShop 9.1.5 or 8.2.8. No workaround is given. The same flawed legacy back-office controller is also present in 1.7.x and earlier, which the project says are end of life and will not be patched.