Wagtail CMS CVE-2026-44201
MEDIUM
GHSA-p5gm-92h4-6pv6
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Network-reachable API with no authentication by default; only partial confidentiality loss (metadata filenames only, no file content or integrity/availability impact).
Primary rating from GitHub Advisory.
CVSS VectorGitHub Advisory
Lifecycle Timeline
3DescriptionGitHub Advisory
Impact
The Documents and Images API incorrectly listed items in private collections. A user with access to the API could see the filename and name of documents and images in private collections.
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
Site owners using Wagtail's API can avoid the vulnerability by adding authentication to the Documents and Images APIs.
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
Wagtail's Documents and Images API endpoints expose private collection metadata to any caller who can reach the API, bypassing the CMS's collection-level access controls. Sites running Wagtail < 7.0.7 or Wagtail 7.1.x-7.3.1 with the API feature enabled leak filenames and display names of documents and images that administrators placed in private collections. No active exploitation has been identified (EPSS 0.03%, absent from CISA KEV), but the flaw is automatable against default unauthenticated API configurations, making bulk reconnaissance straightforward for any network-adjacent attacker.
Technical ContextAI
Wagtail (pip/wagtail) is a Django-based content management system providing a RESTful API v2 for headless deployments. Collections in Wagtail serve as permission-scoped groupings; marking a collection private is intended to restrict visibility of its contents. CWE-280 (Improper Handling of Insufficient Permissions or Privileges) identifies the root cause: the /api/v2/documents/ and /api/v2/images/ listing endpoints enumerated all registered items without checking the privacy status of the parent collection, returning metadata to callers who should have been excluded. Affected CPE pkg:pip/wagtail covers versions < 7.0.7 and >= 7.1.0, < 7.3.2 as confirmed by NVD and the GitHub Advisory GHSA-p5gm-92h4-6pv6.
RemediationAI
Vendor-released patches are available: upgrade to Wagtail 7.0.7 for deployments on the 7.0.x branch, or Wagtail 7.3.2 for deployments on 7.1.x through 7.3.x; new deployments should target Wagtail 7.4 LTS which also includes the fix. The full advisory is at https://github.com/wagtail/wagtail/security/advisories/GHSA-p5gm-92h4-6pv6. For sites that cannot patch immediately, Wagtail's documented workaround is to enable authentication on the Documents and Images API endpoints as described at https://docs.wagtail.org/en/stable/advanced_topics/api/v2/configuration.html#authentication. Adding authentication eliminates unauthenticated enumeration entirely; the trade-off is that legitimate public or headless consumers of these endpoints will require credentials, which may break public-facing read-only API integrations and require client-side changes.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today