PrestaShop XSS can be stored in DB from "add a message form" in order detail page (FO)
Impact
The isCleanHtml method is not used on this this form, which makes it possible to store an xss in DB. The impact is low because the html is not interpreted in BO, thanks to twig's escape mechanism. In FO, the xss is effective, but only impacts the customer sending it, or the customer session from which it was sent.
Source excerpt · OSVAffected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| Earlier releases before 8.1.3Ecosystem versions | 8.1.3 |
Version evidence: OSV · GHSA-vr7m-r9vm-m4wf
View original version evidence (92 explicit versions)
Original source description
Impact
The isCleanHtml method is not used on this this form, which makes it possible to store an xss in DB. The impact is low because the html is not interpreted in BO, thanks to twig's escape mechanism. In FO, the xss is effective, but only impacts the customer sending it, or the customer session from which it was sent.
Be careful if you have a module fetching these messages from the DB and displaying it without escaping html.
Patches
8.1.x
Reporter
Reported by Rona Febriana (linkedin: https://www.linkedin.com/in/rona-febriana/)
References
- Security advisory github.com/PrestaShop/PrestaShop/security/advisories/GHSA-vr7m-r9vm-m4wf
- Security advisory nvd.nist.gov/vuln/detail/CVE-2024-21628
- Patch github.com/PrestaShop/PrestaShop/commit/afc45b93b3cc33be0e571559d2838c6960d98856
- Patch github.com/PrestaShop/PrestaShop/commit/c3d78b7e49f5fe49a9d07725c3174d005deaa597
- Source reference github.com/PrestaShop/PrestaShop