How severe is GHSA-xfm3-hjcc-gv78?

GHSA-xfm3-hjcc-gv78 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-xfm3-hjcc-gv78?

GHSA-xfm3-hjcc-gv78 affects the following packages: prestashop/blockreassurance (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-xfm3-hjcc-gv78?

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

How do I detect GHSA-xfm3-hjcc-gv78 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-xfm3-hjcc-gv78 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-xfm3-hjcc-gv78 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xfm3-hjcc-gv78 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-xfm3-hjcc-gv78?

GHSA-xfm3-hjcc-gv78 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th 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-xfm3-hjcc-gv78?

GHSA-xfm3-hjcc-gv78 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xfm3-hjcc-gv78 published, and has it been updated?

GHSA-xfm3-hjcc-gv78 was published on November 9, 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

Any value can be changed in the configuration table by an employee having access to block reassurance moduleGHSA-xfm3-hjcc-gv78

MEDIUMFix: PrestaShop/blockreassurance@0a74bf1

GHSA-xfm3-hjcc-gv78 is a medium-severity (CVSS 5.3) CWE-284 vulnerability in prestashop/blockreassurance. A fix is available for prestashop/blockreassurance — see the affected versions and patch details below.

Also known asCVE-2023-47110

Published

Nov 9, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 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-xfm3-hjcc-gv78.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.09%

Lower risk than most CVEs44th percentile — riskier than 44% 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

blockreassurance adds an information block aimed at offering helpful information to reassure customers that their store is trustworthy. An ajax function in module blockreassurance allows modifying any value in the configuration table. This vulnerability 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-xfm3-hjcc-gv78 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact An ajax function in module blockreassurance allows modifying any value in the configuration table ### Patches v5.1.4 ### Workarounds no workaround available ### References