PrestaShop blockreassurance BO User can remove any file from server when adding a and deleting a block
Published Nov 8, 2023 · Updated Oct 23, 2026 · Also known as GHSA-83j2-qhx2-p7jc
Original summary
Normalized public record · Updated Oct 23, 2026
PrestaShop blockreassurance BO User can remove any file from server when adding a and deleting a block
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Potential 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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- GHSA-83j2-qhx2-p7jc
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Nov 8, 2023 · Last refreshed Oct 23, 2026