Wagtail CMS CVE-2026-44197
MEDIUM
GHSA-c6wj-9vcj-75pj
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Requires authenticated CMS login (PR:L) over the network; sequential PKs make enumeration low-complexity; pure read disclosure yields C:H with no integrity or availability impact.
Primary rating from GitHub Advisory.
CVSS VectorGitHub Advisory
Lifecycle Timeline
3Blast Radius
ecosystem impact- 1 pypi packages depend on wagtail (1 direct, 0 indirect)
Ecosystem-wide dependent count for version 7.1.
DescriptionGitHub Advisory
Impact
A CMS user without the ability to edit a page could access revisions of the page through the revision compare view if they knew the primary key of two revisions. This could potentially result in disclosure of sensitive information.
Patches
Patched versions have been released as Wagtail 7.0.7 and 7.3.2. The new 7.4 LTS feature release also incorporates this fix.
Workarounds
No workaround is available.
Acknowledgements
Many thanks to Seoyoung Kang @seoyoung-kang from AhnLab and an independent security researcher 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](mailto:security@wagtail.org) (view the security policy for more information).
AnalysisAI
Unauthorized revision disclosure in Wagtail CMS allows authenticated CMS users lacking page-edit permissions to read historical page revisions through the revision compare view by supplying known or guessed revision primary keys. Affected installations running Wagtail versions below 7.0.7 or between 7.1 and 7.3.2 (exclusive) expose draft and revision content to lower-privileged CMS accounts. No public exploit code has been identified and CISA KEV does not list this vulnerability; EPSS at 0.03% (8th percentile) and SSVC exploitation status of 'none' together indicate low real-world exploitation activity at time of analysis.
Technical ContextAI
Wagtail is a Python/Django-based CMS distributed via PyPI (pkg:pip/wagtail). Its admin interface includes a revision compare view that renders a diff between two historical snapshots of a page, identified by integer primary keys. CWE-280 (Improper Handling of Insufficient Permissions or Privileges) describes the root cause: the revision compare view endpoint failed to assert that the requesting user holds page-edit permission before returning revision content, relying only on general CMS authentication. Because Django model primary keys are typically sequential integers, an authenticated but low-privileged CMS user can enumerate or guess valid revision PKs and craft a direct request to the compare view URL, bypassing the intended authorization boundary. The vulnerability is scoped to information disclosure with no write or execution surface.
RemediationAI
Upgrade Wagtail to version 7.0.7 (for deployments on the 7.0.x branch) or 7.3.2 (for deployments on 7.1-7.3.x); the 7.4 LTS release also includes the fix and is recommended for long-term support. The vendor advisory at https://github.com/wagtail/wagtail/security/advisories/GHSA-c6wj-9vcj-75pj confirms no workaround is available for unpatched versions. As a compensating control in environments where immediate patching is not feasible, network-layer access to the Wagtail admin interface should be restricted to trusted IP ranges via firewall or reverse-proxy rules, which limits exposure to insider accounts already present in your CMS. Note that IP restriction does not eliminate the vulnerability for users already inside the allowed range; patching remains the only definitive fix.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today