Medium

PrestaShop XSS can be stored in DB from "add a message form" in order detail page (FO)

  • Disclosed: 03.01.2024
  • Updated: 11.10.2026 10:22

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/)

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package prestashop/prestashop < 8.1.3 8.1.3
PrestaShop (core) prestashop/prestashop < 8.1.3 8.1.3

References

CVSS score 5.4/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:L
Weakness (CWE)
CWE-79
Platform
Composer, PrestaShop
Package
prestashop/prestashop
Disclosed
03.01.2024
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-vr7m-r9vm-m4wf - CC BY 4.0

Vulnerability history: prestashop/prestashop

All published vulnerabilities of this package (PrestaShop (core)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (32) in the archive
Total entries
32
First → latest
01.2020 05.2026
Without a fix
9
Exploited in attacks
1

Severity breakdown

  • Critical 6
  • High 8
  • Medium 17
  • Low 1

Disclosures per year

  1. 2020: 1
  2. 2021: 1
  3. 2022: 10
  4. 2023: 10
  5. 2024: 5
  6. 2025: 1
  7. 2026: 4
Severity:
  1. Critical · 9.3 CVE-2026-44212 < 8.2.6, >= 9.0.0, < 9.1.1 8.2.6, 9.1.1
  2. High · 7.6 CVE-2026-33673 >= 9.0.0-alpha.1, < 9.1.0, < 8.2.5 9.1.0, 8.2.5
  3. Critical · 9.6 CVE-2024-34716 >= 8.1.0, < 8.1.6 8.1.6
  4. PrestaShop XSS can be stored in DB from "add a message form" in order detail page (FO) this entry
    Medium · 5.4 CVE-2024-21628 < 8.1.3 8.1.3
  5. High · 8.1 CVE-2024-21627 >= 8.0.0-beta.1, < 8.1.3, < 1.7.8.11 8.1.3, 1.7.8.11
  6. High · 8.3 CVE-2023-39527 >= 8.0.0, < 8.0.5, < 1.7.8.10 no fix
  7. Critical · 9.8 CVE-2022-31181 >= 1.6.0.10, < 1.7.8.7 1.7.8.7
  8. High · 8.8 CVE-2018-20717 < 1.7.2.5 1.7.2.5
  9. High · 8.0 CVE-2023-30838 >= 8.0.0, < 8.0.3, < 1.7.8.8 no fix
  10. Critical · 9.0 CVE-2022-21686 >= 1.7.0.0, < 1.7.8.3 1.7.8.3
  11. High · 7.5 CVE-2021-43789 >= 1.7.5.0, < 1.7.8.2 1.7.8.2
  12. Critical · 9.8 Exploited in attacks CVE-2017-9841 < 1.7.6.0 no fix

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.