How severe is GHSA-83j2-qhx2-p7jc?

GHSA-83j2-qhx2-p7jc has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-83j2-qhx2-p7jc?

GHSA-83j2-qhx2-p7jc affects the following packages: prestashop/blockreassurance (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-83j2-qhx2-p7jc?

Update prestashop/blockreassurance to 5.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-83j2-qhx2-p7jc is resolved across your whole dependency graph.

How do I detect GHSA-83j2-qhx2-p7jc in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for prestashop/blockreassurance, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-83j2-qhx2-p7jc 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.

Is GHSA-83j2-qhx2-p7jc actively exploited in the wild?

No public exploit code has been indexed for GHSA-83j2-qhx2-p7jc 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 is the EPSS score for GHSA-83j2-qhx2-p7jc?

GHSA-83j2-qhx2-p7jc has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-83j2-qhx2-p7jc?

GHSA-83j2-qhx2-p7jc is classified as CWE-285 (CWE-285). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-83j2-qhx2-p7jc published, and has it been updated?

GHSA-83j2-qhx2-p7jc was published on November 8, 2023 and was last updated on September 10, 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

MEDIUM severity

PrestaShop blockreassurance BO User can remove any file from server when adding a and deleting a blockGHSA-83j2-qhx2-p7jc

MEDIUMFix: PrestaShop/blockreassurance@2d0e97b

GHSA-83j2-qhx2-p7jc is a medium-severity (CVSS 5.5) CWE-285 vulnerability in prestashop/blockreassurance. A fix is available for prestashop/blockreassurance — see the affected versions and patch details below.

Also known asCVE-2023-47109

Published

Nov 8, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-83j2-qhx2-p7jc.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk+0.19%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘prestashop/blockreassurance

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

PrestaShop blockreassurance adds an information block aimed at offering helpful information to reassure customers that the store is trustworthy. When adding a block in blockreassurance module, a BO user can modify the http request and give the path of any file in the project instead of an image. When deleting the block from the BO, the file will be deleted. It is possible to make the website completely unavailable by removing index.php for example. This issue has been patched in version 5.1.4.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`prestashop/blockreassurance`	all versions	5.1.4`composer require prestashop/blockreassurance:^5.1.4`

Affected Products

1 product · 1 configurations

Application

customer reassurance blockprestashop

< 5.1.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for prestashop/blockreassurance, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update prestashop/blockreassurance to 5.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-83j2-qhx2-p7jc 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.

Frequently Asked Questions

### Impact When adding a block in blockreassurance module, a BO user can modify the http request and give the path of any file in the project instead of an image. When deleting the block from the BO, the file will be deleted. It is possible to make the website completely unavailable by removing index.php for example. ### Patches v5.1.4 ### Workarounds No workaround available ### References