How severe is GHSA-8r4m-5p6p-52rp?

GHSA-8r4m-5p6p-52rp has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8r4m-5p6p-52rp?

GHSA-8r4m-5p6p-52rp affects the following packages: prestashop/prestashop (Packagist), prestashop/prestashop (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-8r4m-5p6p-52rp?

Update prestashop/prestashop to 8.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8r4m-5p6p-52rp is resolved across your whole dependency graph.

How do I detect GHSA-8r4m-5p6p-52rp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for prestashop/prestashop. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8r4m-5p6p-52rp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8r4m-5p6p-52rp?

O3 pinpoints whether GHSA-8r4m-5p6p-52rp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8r4m-5p6p-52rp actively exploited in the wild?

No public exploit code has been indexed for GHSA-8r4m-5p6p-52rp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-8r4m-5p6p-52rp?

GHSA-8r4m-5p6p-52rp is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-8r4m-5p6p-52rp published, and has it been updated?

GHSA-8r4m-5p6p-52rp was published on April 26, 2023 and was last updated on July 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

GHSA-8r4m-5p6p-52rp

HIGHFix: PrestaShop/PrestaShop@cddac41

GHSA-8r4m-5p6p-52rp is a high-severity (CVSS 7.7) SQL Injection vulnerability in prestashop/prestashop. O3 Security confirms whether GHSA-8r4m-5p6p-52rp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Arbitrary file read via SQL injection

Also known asCVE-2023-30545

Published

Apr 26, 2023

Updated

Jul 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Jul 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘prestashop/prestashop🐘prestashop/prestashop

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

It is possible for a user having access to the SQL Manager (Advanced Options -> Database) to arbitrary read any file on the Operating system when using SQL function LOAD_FILE in a SELECT request. So It can access to critical information.

Patches

The patch will be on PS 8.0.4 and PS 1.7.8.9

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`prestashop/prestashop`	≥ 8.0.0&&< 8.0.4	8.0.4
🐘Packagist	`prestashop/prestashop`	all versions	1.7.8.9

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for prestashop/prestashop. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update prestashop/prestashop to 8.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8r4m-5p6p-52rp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8r4m-5p6p-52rp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8r4m-5p6p-52rp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact It is possible for a user having access to the SQL Manager (Advanced Options -> Database) to arbitrary read any file on the Operating system when using SQL function LOAD_FILE in a SELECT request. So It can access to critical information. ### Patches The patch will be on PS 8.0.4 and PS 1.7.8.9

O3 Security · Impact-Aware SCA

Is GHSA-8r4m-5p6p-52rp in your dependencies?

O3 detects GHSA-8r4m-5p6p-52rp across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works