CVE-2026-25517

Description

### 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](https://docs.wagtail.io/en/stable/support.html) - Send an email to [security@wagtail.org](mailto:security@wagtail.org) (view our [security policy](https://github.com/wagtail/wagtail/security/policy) for more information).

How to fix CVE-2026-25517

To remediate CVE-2026-25517, upgrade the affected package to a fixed version below.

• —upgrade to 6.3.6 or later

Is CVE-2026-25517 being exploited?

Low — EPSS is 0.0%, meaning exploitation activity has not been observed at scale.

Affected packages (1)

• from 0, < 6.3.6

CVSS scores

References (13)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-25517
• PATCHgithub.com/wagtail/wagtail
• WEBgithub.com/wagtail/wagtail/commit/01fd3477365a193e6a8270311defb76e890d2719
• WEBgithub.com/wagtail/wagtail/commit/5f09b6da61e779b0e8499bdbba52bf2f7bd3241f