Improper validation of URLs ('Cross-site Scripting') in Wagtail rich text fields
- 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 2.11.7, 2.11.6, 2.12.4
- 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
Summary
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).
Timeline
- CVE published
- Record last updated
Affected versions
- wagtail wagtail
through 2.11.6; From 2.12 · through 2.12.3
- wagtailPyPI
From 2.11 · fixed in 2.11.7; fixed in 2.11.6; From 2.12 · fixed in 2.12.4
- wagtailPyPI
fixed in 2.11.7
- wagtailPyPI
From 2.12 · fixed in 2.12.4