Improper validation of URLs ('Cross-site Scripting') in Wagtail rich text fields
wagtail
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wagtail PyPI |
|
|
wagtail
| Product | Affected | Fixed in |
|---|---|---|
| wagtail PyPI |
|
|
Wagtail is a Django content management system. In affected versions of Wagtail, when saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. See referenced GitHub advisory for additional details, including a workaround. Patched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch).
From the CVE record · GitHub_M
Affected Wagtail versions do not check link URL protocols server-side when saving rich text in the admin interface. A malicious user with admin access can craft a POST request to publish content containing `javascript:` URLs with arbitrary code. An ordinary site visitor cannot exploit this without admin access.
Check deployments running Wagtail before 2.11.7 or Wagtail 2.12 before 2.12.4.