CVE-2026-25517
Missing Permission Check in Wagtail Preview Enables Data Exposure
Publication date: 2026-02-04
Last updated on: 2026-02-20
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| torchbox | wagtail | to 6.3.6 (exc) |
| torchbox | wagtail | From 6.4 (inc) to 7.0.4 (exc) |
| torchbox | wagtail | From 7.1 (inc) to 7.1.3 (exc) |
| torchbox | wagtail | From 7.2 (inc) to 7.2.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-25517 is a security vulnerability in the Wagtail content management system affecting versions prior to 6.3.6, 7.0.4, 7.1.3, 7.2.2, and 7.3. The issue arises from missing permission checks on preview endpoints for pages, snippets, and site settings.'}, {'type': 'paragraph', 'content': "A user with access to the Wagtail admin interface and knowledge of a model's fields can craft a form submission to generate a preview rendering of any page, snippet, or site setting object with preview enabled, using arbitrary data supplied by the user. Although the existing data of the object is not exposed, the rendered preview may leak other database contents depending on the template, potentially revealing information normally restricted to users with edit permissions."}, {'type': 'paragraph', 'content': 'This vulnerability cannot be exploited by ordinary site visitors without admin access. The root cause is a missing authorization check on preview endpoints, allowing unauthorized preview rendering.'}] [4, 5, 6]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized exposure of sensitive or unpublished content within the Wagtail CMS. Specifically, an attacker with admin access but insufficient permissions can preview pages, snippets, or site settings with arbitrary data, potentially leaking other database contents embedded in the templates.
The impact is primarily a confidentiality breach, as it may reveal information that should be restricted to users with edit permissions. There are no known impacts on data integrity or system availability.
Exploitation requires network access and admin privileges, but no user interaction, making it a moderate risk with a CVSS score of 5.1.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves missing permission checks on Wagtail CMS preview endpoints accessible only to users with admin access. Detection involves verifying if unauthorized users can access preview endpoints for pages, snippets, or site settings without proper permissions.
Since the vulnerability requires admin access and crafted form submissions to preview content, detection can include monitoring HTTP POST requests to preview endpoints in the Wagtail admin interface for unusual or unauthorized preview attempts.
Specific commands are not provided in the available resources. However, network monitoring tools like tcpdump or Wireshark can be used to capture HTTP traffic to the Wagtail admin preview URLs, and web server logs can be inspected for suspicious POST requests to preview endpoints.
Additionally, reviewing user permissions in the Wagtail admin and checking for unexpected access or form submissions to preview endpoints may help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade Wagtail CMS to a patched version where this vulnerability is fixed. The patched versions are 6.3.6, 7.0.4, 7.1.3, 7.2.2, and 7.3.
No workarounds are available, so applying the official security update is essential to ensure proper permission checks are enforced on preview endpoints.
Restrict access to the Wagtail admin interface to trusted users only, as the vulnerability requires admin access to exploit.
Review and audit user permissions regularly to ensure that only authorized users have access to preview and edit content.