Skip to content

Wagtail: Improper restriction handling on descendant collections in Documents and Images API

Moderate severity GitHub Reviewed Published Aug 20, 2026 in wagtail/wagtail • Updated Aug 20, 2026

Package

pip wagtail (pip)

Affected versions

< 7.0.9
>= 7.1, < 7.3.4
>= 7.4, < 7.4.3
= 8.0rc1

Patched versions

7.0.9
7.3.4
7.4.3
8.0rc2

Description

Impact

The Documents and Images API V2 incorrectly listed items in descendants of private collections, which should inherit the view restrictions defined on their ancestors. A user with access to the API could see the filename and name of documents and images in these descendant collections.

Patches

Patched versions have been released as Wagtail 7.0.9, 7.3.4, 7.4.3 and 8.0rc2.

Workarounds

Site owners using Wagtail's API can avoid the vulnerability by adding authentication to the Documents and Images APIs.

Acknowledgements

Many thanks to Ta Duc Thien for reporting this issue.

For more information

If you have any questions or comments about this advisory:

References

@gasman gasman published to wagtail/wagtail Aug 20, 2026
Published to the GitHub Advisory Database Aug 20, 2026
Reviewed Aug 20, 2026
Last updated Aug 20, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

Weaknesses

Improper Handling of Insufficient Permissions or Privileges

The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-c2xx-cjmh-9q8f

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.