CVE-2026-44197: Wagtail: Improper permission handling when comparing revisions
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 (view the security policy for more information).
Other sources
Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, 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. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44197?
CVE-2026-44197 has been assessed to pose a risk of sensitive information disclosure.
How do I fix CVE-2026-44197?
To fix CVE-2026-44197, upgrade to wagtail version 7.3.2 or later, or to version 7.0.7 if remaining below that version.
What impact does CVE-2026-44197 have on users?
CVE-2026-44197 allows unauthorized users to view page revisions, potentially leading to exposure of sensitive content.
Which versions of wagtail are affected by CVE-2026-44197?
Wagtail versions from 7.1 up to 7.3.1 and below 7.0.7 are affected by CVE-2026-44197.
Who is at risk from CVE-2026-44197?
CMS users without edit permissions who can access revision compare views are at risk from CVE-2026-44197.