Database modification via development-only query rejection
Published Apr 25, 2023 · Updated Feb 3, 2025
SQL injection in PrestaShop before 1.7.8.9 and 8.0.0 through 8.0.3 allows remote authenticated users to alter database data via SQL Manager. Db::executeS checks for a read-only SQL verb but, outside developer mode, passed rejected statements to execute(), allowing SQL Manager filtering to reach write operations. Any back-office user who can submit a SQL Manager query can write, update, or delete database records without the corresponding database rights.
Summary
What happened
SQL injection in PrestaShop before 1.7.8.9 and 8.0.0 through 8.0.3 allows remote authenticated users to alter database data via SQL Manager. Db::executeS checks for a read-only SQL verb but, outside developer mode, passed rejected statements to execute(), allowing SQL Manager filtering to reach write operations. Any back-office user who can submit a SQL Manager query can write, update, or delete database records without the corresponding database rights.
The record
- CVE
- CVE-2023-30839
- Published
- Apr 25, 2023
- Updated
- Feb 3, 2025
- Vendor
- PrestaShop
- Product
- PrestaShop
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.7.8.9
- Affected versionversion=>= 8.0.0, < 8.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo