Wagtail: Improper restriction handling on Page translation API endpoint
- 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
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Medium (ghsa)
- 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
Summary
Wagtail, an open-source Python content management system, is affected. A user with translation-submission permissions could use the admin API's "copy for translation" feature to view the contents of existing pages they are not authorized to edit.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Impact A CMS user with the "submit translations" permission, could use the Admin API's "copy for translation" endpoint to copy an existing page that they do not have edit access to, allowing them to view its contents. Patches Patched versions have been released as Wagtail 7.0.9, 7.3.4, 7.4.3 and 8.0rc2. Workarounds N/A Acknowledgements Many thanks to tinyb0y for reporting this issue. For more information If you have any questions or comments about this advisory: • Visit Wagtail's support channels • Email us at security@wagtail.org (view our security policy for more information).
Timeline
- Advisory published
- Record last updated
Affected versions
- wagtailPyPI
fixed in 7.0.9
- wagtailPyPI
From 7.1rc1 · fixed in 7.3.4
- wagtailPyPI
From 7.4rc1 · fixed in 7.4.3
- wagtailPyPI
From 8.0rc1 · fixed in 8.0rc2