SQL Injection in prestashop/prestashop (CVE-2023-30545)
Summary
SQL injection in prestashop/prestashop (CVE-2023-30545). Confidential information can be exposed externally. Mitigation: upgrade to 1.7.8.9 or later.
Original description
The description as published by the source.
PrestaShop is an Open Source e-commerce web application. Prior to versions 8.0.4 and 1.7.8.9, it is possible for a user with access to the SQL Manager (Advanced Options -> Database) to arbitrarily read any file on the operating system when using SQL function LOAD_FILE in a SELECT request. This gives the user access to critical information. A patch is available in PrestaShop 8.0.4 and PS 1.7.8.9
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-30545 has been found in prestashop/prestashop.
Confidential information can be exposed externally.
What to do: upgrade prestashop/prestashop to 1.7.8.9 or later.
If unsure, ask your IT team or search "prestashop/prestashop CVE-2023-30545" on the vendor's site.
CVE-2023-30545 (prestashop/prestashop) — CWE-89
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.7.8.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in prestashop/prestashop.
Check the vendor advisory for the affected versions of prestashop/prestashop.
Severity: ?. Confidential information can be exposed externally.
Update to 1.7.8.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'prestashop/prestashop' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'prestashop/prestashop' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
prestashop/prestashopを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade prestashop/prestashop to 1.7.8.9ステージング環境で 1.7.8.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com