Wagtail: Improper escaping of HTML (Cross-site Scripting) on TableBlock class attributes
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.3.8, 7.0.6, 7.2.3, 7.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Wagtail 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- wagtail wagtail
fixed in 6.3.8; From 6.4rc1 · fixed in 7.0.6; From 7.1rc1 · fixed in 7.2.3; From 7.3rc1 · fixed in 7.3.1
- wagtailPyPI
fixed in 6.3.8; From 6.4 · fixed in 7.0.6; From 7.1 · fixed in 7.2.3
- wagtailPyPI
fixed in 6.3.8
- wagtailPyPI
From 6.4rc1 · fixed in 7.0.6
- wagtailPyPI
From 7.1rc1 · fixed in 7.2.3
- wagtailPyPI
From 7.3rc1 · fixed in 7.3.1