Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-gf46-prm4-56pc

CRITICALFix: PrestaShop/PrestaShop@817847e

GHSA-gf46-prm4-56pc is a critical-severity (CVSS 9.1) SQL Injection vulnerability in prestashop/prestashop. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-gf46-prm4-56pc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

PrestaShop SQL manager vulnerability

Also known asCVE-2023-39526
Published
Aug 9, 2023
Updated
Jul 16, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known

Real-World Exposure

3 pkgs affected
🐘prestashop/prestashop🐘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

Remote code execution through SQL injection and arbitrary file write in back office

Patches

1.7.8.10 8.0.5 8.1.1

Found by

Truff (via yeswehack)

Workarounds

none

References

none

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistprestashop/prestashop8.1.0&&< 8.1.18.1.1
🐘Packagistprestashop/prestashop8.0.0&&< 8.0.58.0.5
🐘Packagistprestashop/prestashopall versions1.7.8.10
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update prestashop/prestashop to 8.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gf46-prm4-56pc is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-gf46-prm4-56pc 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-gf46-prm4-56pc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Remote code execution through SQL injection and arbitrary file write in back office ### Patches 1.7.8.10 8.0.5 8.1.1 ### Found by Truff (via yeswehack) ### Workarounds none ### References none
O3 Security · Impact-Aware SCA

Is GHSA-gf46-prm4-56pc in your dependencies?

O3 detects GHSA-gf46-prm4-56pc across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.