Wagtail: Improper restriction handling on Pages admin API
- 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 7.0.9, 7.3.4, 7.4.3, 8.0rc2
- 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. Prior to versions 7.0.9, 7.3.4, 7.4.3, and 8.0rc2 on their respective release lines, the internal Pages admin API returns page fields declared in api_fields without sufficient access control, allowing a user with Wagtail admin access to retrieve restricted draft and live page content. This issue is fixed in versions 7.0.9, 7.3.4, 7.4.3, and 8.0rc2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- wagtail wagtail
fixed in 7.0.9; From 7.1 · fixed in 7.3.4; From 7.4 · fixed in 7.4.3; From 8.0rc1 · fixed in 8.0rc2
- wagtailPyPI
fixed in 7.0.9
- wagtailPyPI
From 7.1 · fixed in 7.3.4
- wagtailPyPI
From 7.4 · fixed in 7.4.3
- wagtailPyPI
From 8.0rc1 · fixed in 8.0rc2
- wagtailPyPI
fixed in 7.0.9; From 7.1 · fixed in 7.3.4; From 7.4 · fixed in 7.4.3; From 8.0rc1 · fixed in 8.0rc2