CVE-2026-44198: Wagtail: Improper permission handling when viewing page history
Impact
A CMS user without the ability to edit a page could still access the history report for the page, potentially resulting 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
Wagtail thanks Seoyoung Kang @seoyoung-kang who is from AhnLab and also 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 still access the history report for the page, potentially resulting 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-44198?
CVE-2026-44198 has a moderate severity rating due to the potential for unauthorized access to sensitive historical data.
How do I fix CVE-2026-44198?
To fix CVE-2026-44198, upgrade to Wagtail version 7.0.7 or later, specifically 7.3.2 or the latest 7.4 LTS release.
What systems are affected by CVE-2026-44198?
CVE-2026-44198 affects Wagtail versions prior to 7.0.7 and between 7.1 and 7.3.2.
What type of vulnerability is CVE-2026-44198?
CVE-2026-44198 is a information disclosure vulnerability that allows unauthorized access to page history reports.
Who is impacted by CVE-2026-44198?
Users of Wagtail who lack edit permissions but can access page history may be impacted by CVE-2026-44198.