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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.5 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H

EPSS

• CVE-2023-47109: 0.77% estimated exploitation activity in the next 30 days; percentile 55.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

8 Nov 2023, 17:53 UTC

Last modified by the source

9 Nov 2023, 16:14 UTC

Source last checked

26 Oct 2026, 14:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-83j2-qhx2-p7jc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-47109

Advisory: PrestaShop blockreassurance BO User can remove any file from server when adding a and deleting a block
IDs: CVE-2023-47109, GHSA-83j2-qhx2-p7jc
Record: https://patchnext.com/advisories/cve-2023-47109 (revision 1, source checked 26 Oct 2026, 14:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: prestashop/blockreassurance 5.1.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist prestashop/blockreassurance: affected <= 5.1.3; fixed in 5.1.4

## Suggested inspection (read-only)
- Packagist prestashop/blockreassurance: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on prestashop/blockreassurance.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-83j2-qhx2-p7jc (GitHub-reviewed advisory GHSA-83j2-qhx2-p7jc lists affected ranges: Packagist prestashop/blockreassurance >=0 <=5.1.3)

Commands are suggestions: review each one before running it.