Authorization bypass in PrestaShop Webservice API via id_shop parameter
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-863.
Summary
PrestaShop before 8.2.9 and from 9.0.0 before 9.2.1 has an authorization flaw in its Webservice API, classified as CWE-863 (Incorrect Authorization). An attacker holding a key restricted to one shop can submit requests with id_shop=all or id_shop_group=N to act on data of every shop, including customer records with email addresses, secure_key values and password hashes. The attacker needs only a valid low-privilege key, and a public proof of concept is referenced.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
Description from the CNA
PrestaShop before 8.2.9 and 9.2.1 contains an authorization flaw in the Webservice API that allows an attacker holding a key restricted to one shop to act on data of every shop by submitting requests with id_shop=all or id_shop_group=N, which expand the shop context without validating the key's actual shop associations and cause shopHasRight() to evaluate the expanded set as a disjunction. Attackers can exploit this flaw via classes/webservice/WebserviceRequest.php to read, modify, or delete data belonging to shops they are not authorized for, including full customer records such as email addresses, secure_key, and password hashes across the installation.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| PrestaShop | PrestaShop | before 8.2.9; 9.0.0 to before 9.2.1 | 8.2.9, 9.2.1 | Patch available | CNA |
- PrestaShop VendorPrestaShop Affected before 8.2.9; 9.0.0 to before 9.2.1 Fixed in 8.2.9, 9.2.1 Patch available CNA
CPE names Threatist (inferred) · 1
Inferred from how NVD named this product before; not given by a source.
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:prestashop:prestashop:*:*:*:*:*:*:*:* | — | — | PrestaShop |
- cpe:2.3:a:prestashop:prestashop:*:*:*:*:*:*:*:* Versions — — ·PrestaShop
Remediation
Update PrestaShop to version 8.2.9 or 9.2.1, which fix the flaw. The sources list no other fixed versions for PrestaShop.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
- Fix · CNA PrestaShop (PrestaShop) Fixed in 8.2.9, 9.2.1
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
PrestaShop 8.2.9, 9.2.1
2 records Highest priority Priority HIGH 1 HIGH, 1 LOW
Other records, highest priority first
- TI-2026-91822 PrestaShop Webservice API authorization bypass enables account takeoverPriority LOW 38
Timeline
- 2026-11-13 Threatist record created from CVE-2026-71531
- 2026-11-15 1 new reference · CNA
- 2026-11-16 CISA SSVC decision points changed
References
Exploit 1
More PrestaShop vulnerabilities
- TI-2024-27717 An issue in Prestashop v.8.1.7 and before allows a remote attacker to execute arbitrary… CVSS 3.1CRITICAL 9.8
- TI-2023-14167 Prestashop posstaticfooter <= 1.0.0 is vulnerable to SQL Injection via posstaticfooter::getPosCurrentHook(). CVSS 3.1CRITICAL 9.8
- TI-2023-14166 Prestashop possearchproducts 1.7 is vulnerable to SQL Injection via PosSearch::find(). CVSS 3.1CRITICAL 9.8
- TI-2023-10662 PrestaShop dpdfrance <6.1.3 is vulnerable to SQL Injection via dpdfrance/ajax.php. CVSS 3.1CRITICAL 9.8
- TI-2024-23013 PrestaShop vulnerable to XSS via customer contact form in FO, through file upload CVSS 3.1CRITICAL 9.7
- TI-2023-14154 An SQL injection vulnerability in the Payplug (payplug) module for PrestaShop, in… CVSS 3.1CRITICAL 9.8
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences