Wagtail CMS CVE-2026-44200
MEDIUM
GHSA-67rv-mg8q-5pf3
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
PR:L reflects mandatory authenticated CMS account; C:H for full restricted page content exposure; I:L added over vendor score to reflect potential unauthorized publish action described in the advisory.
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 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](mailto:security@wagtail.org) (view the security policy for more information).
AnalysisAI
Improper permission enforcement in Wagtail's page copy feature allows authenticated low-privilege CMS users to exfiltrate and potentially publish page content they are not authorized to access. Affected versions include all Wagtail releases below 7.0.7 and the 7.1-7.3.x range below 7.3.2. While the CVSS confidentiality impact is rated High (C:H), real-world exploitation probability is very low - EPSS sits at 0.02% (7th percentile), SSVC records no exploitation, and the attack requires an existing CMS account, making this a medium-priority internal threat rather than a perimeter risk. No public exploit code has been identified at time of analysis.
Technical ContextAI
Wagtail is an open-source Django-based content management system distributed as a Python pip package (pkg:pip/wagtail). Its page tree model assigns granular permissions per page node, allowing site administrators to restrict which CMS users can view, edit, or publish specific pages. The vulnerability stems from CWE-280 (Improper Handling of Insufficient Permissions or Privileges): when a user triggers the 'copy page' action, the application correctly validates whether the user has write/create permissions at the copy destination, but entirely omits the authorization check on the source page. This means the permission enforcement is incomplete - half of the two-party access control decision is skipped - allowing the copy to proceed even when the actor is unauthorized to read the source. The flaw exists within Wagtail's internal page management views rather than a public-facing API.
RemediationAI
Upgrade to Wagtail 7.0.7 (for users on the 7.0.x maintenance branch), Wagtail 7.3.2 (for users on the 7.3.x branch), or Wagtail 7.4 LTS, all of which contain the patch. The vendor has confirmed no workaround is available - the page-copy permission bypass cannot be mitigated without applying the patch, since disabling the copy feature entirely would require modifying Wagtail internals. As an interim operational control, site administrators should audit CMS user accounts and restrict the 'can add pages' and 'can copy pages' capabilities to only fully trusted editors until patching is feasible. The vendor advisory is available at https://github.com/wagtail/wagtail/security/advisories/GHSA-67rv-mg8q-5pf3.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today