Wagtail: Improper escaping of HTML (Cross-site Scripting) on TableBlock class attributes
wagtail
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wagtail PyPI |
|
|
wagtail
| Product | Affected | Fixed in |
|---|---|---|
| wagtail PyPI |
|
|
7.3.1Wagtail is an open source content management system built on Django. Prior to versions 6.3.8, 7.0.6, 7.2.3, and 7.3.1, a stored cross-site scripting (XSS) vulnerability exists on rendering TableBlock blocks within a StreamField. A user with access to create or edit pages containing TableBlock StreamField blocks is able to set specially-crafted class attributes on the block which run arbitrary JavaScript code when the page is viewed. When viewed by a user with higher privileges, this could lead to performing actions with that user's credentials. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin, and only affects sites using TableBlock. This issue has been patched in versions 6.3.8, 7.0.6, 7.2.3, and 7.3.1.
From the CVE record · GitHub_M
Wagtail sites using TableBlock within a StreamField are vulnerable to stored cross-site scripting. A user with Wagtail admin access to create or edit affected pages can set a crafted class attribute that runs JavaScript when someone views the page. If a higher-privileged user views it, the script could perform actions with that user's credentials; ordinary site visitors cannot create the payload.
Teams running Wagtail sites that use TableBlock should check installations earlier than 6.3.8, or on affected 6.4–7.0, 7.1–7.2, or 7.3 release lines.