MediumGHSA-83j2-qhx2-p7jcCVE-2023-47109

PrestaShop blockreassurance BO User can remove any file from server when adding a and deleting a block

Published 8 Nov 2023 · Updated 10 Sept 2026

Is your project on an affected prestashop/blockreassurance?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<5.1.4
Fixed in
5.1.4
Update to the fixed version for your release line, for example:composer require prestashop/blockreassurance:^5.1.4

Details

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

Is GHSA-83j2-qhx2-p7jc in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected prestashop/blockreassurance, and gives you the command that fixes it.

More advisories for prestashop/blockreassurance

  • MediumCVE-2023-47110Any value can be changed in the configuration table by an employee having access to block reassurance module · 9 Nov 2023
prestashop/blockreassurance security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.