CVE-2026-33674
Prestashop ≤ 8.2.5
Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:NSummary
CVE-2026-33674 is a low-severity Improper Use of Validation Framework (CWE-1173) vulnerability in Prestashop Prestashop. Its CVSS base score is 2.0 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-16442
Vulnerability Data
PrestaShop is an open source e-commerce web application. Versions prior to 8.2.5 and 9.1.0 improperly use the validation framework. Versions 8.2.5 and 9.1.0 contain a fix. No known workarounds are available.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V2.2.2V1.3.1V1.4.2V15.3.7
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover incorrect or missing use of supplied validation frameworks during development.
SI-10 directly requires checking validity of inputs, which structurally prevents failure to use or misuse of a validation framework.
Requiring documented development processes and tools can mandate correct adoption of language or library validation frameworks.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require correct adoption of language-provided or library input-validation frameworks.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing validation but does not enforce framework adoption.
Secure development life cycle mandates use of approved validation frameworks and libraries.
Application security requirements explicitly call for proper input validation mechanisms.
Secure architecture principles encourage validated input handling but do not prescribe frameworks.
Secure coding directly requires correct use of language-provided or approved validation libraries.