CVE-2026-44200: Wagtail: Improper permission handling when copying pages

Published May 8, 2026
·
Updated

Impact

A CMS user with limited access to pages could copy a page they don't have access to to an area of the site they do. Once copied, they'd be able to view its contents, and potentially publish it. Permissions were correctly checked for the copy destination, but not for the source page.

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 independent security researcher Sanjok Karki @thesanjok 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 with limited access to pages could copy a page they don't have access to to an area of the site they do. Once coped, they'd be able to view its contents, and potentially publish it. Permissions were correctly checked for the copy destination, but not for the source page. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.

— MITRE

Affected Software

4 affected componentsFixes available
pip/wagtail>=7.1<7.3.2
7.3.2
pip/wagtail<7.0.7
7.0.7
Torchbox Wagtail<7.0.7
Torchbox Wagtail>=7.1<7.3.2

Event History

May 8, 2026
Advisory Published
via GitHub·08:23 PM
Data Sourced
via GitHub·08:23 PM
DescriptionSeverityWeaknessAffected Software
May 11, 2026
CVE Published
via MITRE·02:41 PM
Data Sourced
via MITRE·02:41 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-44200?

The severity of CVE-2026-44200 is classified as high due to the potential for unauthorized access to sensitive content.

2

How do I fix CVE-2026-44200?

To fix CVE-2026-44200, upgrade to Wagtail version 7.3.2 or higher, or to version 7.0.7 if using an earlier version.

3

Who is affected by CVE-2026-44200?

Any Wagtail users utilizing versions below 7.3.2 or 7.0.7 are affected by CVE-2026-44200.

4

What types of systems are vulnerable to CVE-2026-44200?

CVE-2026-44200 affects systems using the Wagtail CMS framework with specific versions that lack proper permission checks.

5

What are the potential consequences of CVE-2026-44200?

The potential consequences of CVE-2026-44200 include unauthorized viewing and publishing of restricted content by users with limited access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203