How severe is GHSA-2jx3-5j9v-prpp?

GHSA-2jx3-5j9v-prpp has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2jx3-5j9v-prpp?

GHSA-2jx3-5j9v-prpp affects the following packages: prestashop/blockwishlist (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2jx3-5j9v-prpp?

Update prestashop/blockwishlist to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jx3-5j9v-prpp is resolved across your whole dependency graph.

How do I detect GHSA-2jx3-5j9v-prpp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for prestashop/blockwishlist. 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-2jx3-5j9v-prpp 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-2jx3-5j9v-prpp?

O3 pinpoints whether GHSA-2jx3-5j9v-prpp 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-2jx3-5j9v-prpp actively exploited in the wild?

Yes. There are 6 known exploit references for GHSA-2jx3-5j9v-prpp, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-2jx3-5j9v-prpp?

GHSA-2jx3-5j9v-prpp has an EPSS (Exploit Prediction Scoring System) score of 24.1%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-2jx3-5j9v-prpp?

GHSA-2jx3-5j9v-prpp 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.

Is there exploit tooling available for GHSA-2jx3-5j9v-prpp?

A Nuclei detection template exists for GHSA-2jx3-5j9v-prpp, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-2jx3-5j9v-prpp published, and has it been updated?

GHSA-2jx3-5j9v-prpp was published on June 25, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-2jx3-5j9v-prpp

HIGH

BlockWishList SQL Injection vulnerability

Also known asCVE-2022-31101

Published

Jun 25, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

24.1%probability of exploitation in next 30 days

Moderate Risk98th percentile-32.84%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐘prestashop/blockwishlist

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

An authenticated customer can perform SQL injection

Patches

Issue is fixed in 2.1.1

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`prestashop/blockwishlist`	≥ 2.0.0&&< 2.1.1	2.1.1

Exploits & PoCs

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

EDB-51001webappsphp

Prestashop blockwishlist module 2.1.0 - SQLi

by Karthik UJ · Aug 9, 2022

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for prestashop/blockwishlist. 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/blockwishlist to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jx3-5j9v-prpp 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-2jx3-5j9v-prpp 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-2jx3-5j9v-prpp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact An authenticated customer can perform SQL injection ### Patches Issue is fixed in 2.1.1

O3 Security · Impact-Aware SCA

Is GHSA-2jx3-5j9v-prpp in your dependencies?

O3 detects GHSA-2jx3-5j9v-prpp 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