Summary
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 [email protected] (view our security policy for more information).
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.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
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.
Frequently Asked Questions
- What is CVE-2026-25517? CVE-2026-25517 is a medium-severity missing authorization vulnerability in wagtail (pip), affecting versions < 6.3.6. It is fixed in 6.3.6, 7.0.4, 7.1.3, 7.2.2, 7.3. The application does not perform an authorization check before performing a sensitive operation.
- Which versions of wagtail are affected by CVE-2026-25517? wagtail (pip) versions < 6.3.6 is affected.
- Is there a fix for CVE-2026-25517? Yes. CVE-2026-25517 is fixed in 6.3.6, 7.0.4, 7.1.3, 7.2.2, 7.3. Upgrade to this version or later.
- Is CVE-2026-25517 exploitable, and should I be worried? Whether CVE-2026-25517 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-25517 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-25517?
- Upgrade
wagtailto 6.3.6 or later - Upgrade
wagtailto 7.0.4 or later - Upgrade
wagtailto 7.1.3 or later - Upgrade
wagtailto 7.2.2 or later - Upgrade
wagtailto 7.3 or later
- Upgrade