Security readout for executives and security teams
Plain-English summary
This flaw affects older PrestaShop e-commerce sites and can let an unauthenticated internet attacker take control of the shop server. The vendor rates it critical and provides a fixed release. Treat exposed stores in the affected version range as urgent because compromise could affect orders, customer data, payments-adjacent operations, and store availability.
Executive priority
Immediate remediation is warranted for any affected internet-facing store. The business risk is server takeover with high confidentiality, integrity, and availability impact. Absence from KEV in the bundle lowers certainty about known exploitation, not the technical urgency.
Technical view
PrestaShop versions from 1.6.0.10 before 1.7.8.7 contain an SQL injection issue that can be chained into PHP Eval execution on attacker input. The CVSS 3.1 score is 9.8, network-accessible, low complexity, no privileges, and no user interaction. The listed weaknesses are CWE-89 and CWE-74.
Likely exposure
Internet-facing PrestaShop stores running versions >= 1.6.0.10 and < 1.7.8.7 are the relevant exposure. The source bundle does not identify additional affected products or precise deployment prerequisites beyond the MySQL Smarty cache mitigation note.
Exploitation context
The provided sources support remote code execution potential and critical severity. They do not show CISA KEV listing or cited confirmation of active exploitation, so active exploitation should not be stated from this bundle alone.
Researcher notes
Focus validation on version range, vendor patch status, and whether the MySQL Smarty cache feature exists where upgrades lag. The bundle names the vulnerability class and outcome but does not provide safe endpoint-level validation details or exploitation evidence.
Mitigation direction
- Upgrade affected PrestaShop installations to version 1.7.8.7 or later vendor-fixed guidance.
- If unable to upgrade, delete the MySQL Smarty cache feature per vendor advice.
- Review the PrestaShop advisory and release notes before changing production stores.
- Prioritize backups and a rollback plan before emergency upgrade work.
Validation and detection
- Inventory all PrestaShop stores and record exact running versions.
- Confirm no production instance is >= 1.6.0.10 and < 1.7.8.7.
- Verify the 1.7.8.7 fix or equivalent vendor patch is deployed.
- Check whether the MySQL Smarty cache feature remains present on unupgraded systems.
- Review application logs for suspicious errors or unexpected template/cache behavior.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-31181 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/PrestaShop/PrestaShop/security/advisories/GHSA-hrgx-p36p-89q4CVE reference · x_refsource_CONFIRM
- https://github.com/PrestaShop/PrestaShop/commit/b6d96e7c2a4e35a44e96ffbcdfd34439b56af804CVE reference · x_refsource_MISC
- https://github.com/PrestaShop/PrestaShop/releases/tag/1.7.8.7CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.