Is prestashop/blockreassurance 1.0 vulnerable?
Composer · 3 releases from 1.0.1 to 1.0.6 · latest prestashop/blockreassurance is 6.0.0 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. prestashop/blockreassurance 1.0.6, the last 1.0 release, is affected by 2 known security advisories (2 medium), including CVE-2023-47110, CVE-2023-47109. Upgrade to 5.1.4 or later to fix all of them.
composer require prestashop/blockreassurance:^5.1.4Is your project on an affected prestashop/blockreassurance?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting prestashop/blockreassurance 1.0.6
Any value can be changed in the configuration table by an employee having access to block reassurance module
- Affected
- <5.1.4
- Fixed in
- 5.1.4
PrestaShop blockreassurance BO User can remove any file from server when adding a and deleting a block
- Affected
- <5.1.4
- Fixed in
- 5.1.4
Every prestashop/blockreassurance 1.0.x release
Affected: 1.0.1 to 1.0.6. Latest prestashop/blockreassurance: 6.0.0.
| Version | Known advisories |
|---|---|
| prestashop/blockreassurance 1.0.6 | CVE-2023-47110, CVE-2023-47109 |
| prestashop/blockreassurance 1.0.5 | CVE-2023-47110, CVE-2023-47109 |
| prestashop/blockreassurance 1.0.1 | CVE-2023-47110, CVE-2023-47109 |
Which of your client projects are still on prestashop/blockreassurance 1.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact prestashop/blockreassurance version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other prestashop/blockreassurance versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.