CVE-2023-47110 json
Any value can be changed in the configuration table by an employee having access to block reassurance module
published 2023-11-09 3 y ago modified 2026-09-10 1 mo ago also GHSA-xfm3-hjcc-gv78 , EUVD-2023-3061
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist prestashop/blockreassurance 5.1.4
- prestashop customer_reassurance_block 5.1.4
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | prestashop/blockreassurance | <5.1.4 |
5.1.4 |
Affected products
- PrestaShop blockreassurance
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
github.com
/PrestaShop/blockreassurance/commit/0a74bf1ebb907eef39e235a3a6dca0c28ed3ad23
web
-
github.com
/PrestaShop/blockreassurance/security/advisories/GHSA-xfm3-hjcc-gv78
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-47110
advisory
-
github.com
/PrestaShop/blockreassurance
package
-
github.com
/PrestaShop/blockreassurance/releases/tag/v5.1.4
web
Sources
- CVE List CVE-2023-47110
- GitHub Advisory GHSA-xfm3-hjcc-gv78
- NVD CVE-2023-47110
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.