Wagtail regular expression denial-of-service via search query parsing
- 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 5.2.6, 6.0.6, 6.1.3
- 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: partial
Summary
Wagtail is an open source content management system built on Django. A bug in Wagtail's `parse_query_string` would result in it taking a long time to process suitably crafted inputs. When used to parse sufficiently long strings of characters without a space, `parse_query_string` would take an unexpectedly large amount of time to process, resulting in a denial of service. In an initial Wagtail installation, the vulnerability can be exploited by any Wagtail admin user. It cannot be exploited by end users. If your Wagtail site has a custom search implementation which uses `parse_query_string`, it may be exploitable by other users (e.g. unauthenticated users). Patched versions have been released as Wagtail 5.2.6, 6.0.6 and 6.1.3.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- wagtail wagtail
From 2.0 · fixed in 5.2.6; From 6.0 · fixed in 6.0.6; From 6.1 · fixed in 6.1.3
- wagtailPyPI
From 6.0 · fixed in 6.0.6
- wagtailPyPI
From 6.1 · fixed in 6.1.3
- wagtailPyPI
From 2.0 · fixed in 5.2.6
- wagtailPyPI
From 6.0 · fixed in 6.0.6; From 6.1 · fixed in 6.1.3; From 2.0 · fixed in 5.2.6