CVE-2026-25517: Wagtail has improper permission handling on admin preview endpoints
Impact Due to a missing permission check on the preview endpoints, a user with access to the Wagtail admin and knowledge of a model's fields can craft a form submission to obtain a preview rendering of any page, snippet or site setting object for which previews are enabled, consisting of any data of the user's choosing. The existing data of the object itself is not exposed, but depending on the nature of the template being rendered, this may expose other database contents that would otherwise only be accessible to users with edit access over the model. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.
Patches Patched versions have been released as Wagtail 6.3.6, 7.0.4, 7.1.3 and 7.2.2. The new 7.3 feature release also incorporates this fix.
Workarounds No workaround is available.
Acknowledgements
Many thanks to @thxtech for reporting this issue.
For more information
If there are any questions or comments about this advisory:
- Visit Wagtail's support channels - Send an email to security@wagtail.org (view our security policy for more information).
Other sources
Wagtail is an open source content management system built on Django. Prior to versions 6.3.6, 7.0.4, 7.1.3, 7.2.2, and 7.3, due to a missing permission check on the preview endpoints, a user with access to the Wagtail admin and knowledge of a model's fields can craft a form submission to obtain a preview rendering of any page, snippet or site setting object for which previews are enabled, consisting of any data of the user's choosing. The existing data of the object itself is not exposed, but depending on the nature of the template being rendered, this may expose other database contents that would otherwise only be accessible to users with edit access over the model. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. This issue has been patched in versions 6.3.6, 7.0.4, 7.1.3, 7.2.2, and 7.3.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25517?
CVE-2026-25517 is rated as a high-severity vulnerability due to improper permission handling.
How do I fix CVE-2026-25517?
To fix CVE-2026-25517, upgrade Wagtail to version 7.3 or newer.
What kind of access does the CVE-2026-25517 vulnerability allow?
CVE-2026-25517 allows an authenticated user to preview any page or snippet without proper permission checks.
Which versions of Wagtail are affected by CVE-2026-25517?
Wagtail versions 6.3.6 up to 7.3rc1 are affected by CVE-2026-25517.
Can CVE-2026-25517 be exploited remotely?
CVE-2026-25517 requires an authenticated user, so it is not considered a remote exploitation vulnerability.