GHSA-x5cx-w6p2-mxf2: Medium severity pip/wagtail vulnerability

Published Aug 20, 2026
·
Updated

Impact A CMS user with "add" permission over a snippet model, but not "change" or "view" permission, could copy an existing snippet that they do not have access to, allowing them to view its contents.

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

Workarounds N/A

Acknowledgements Many thanks to tinyb0y for reporting this issue.

For more information If you have any questions or comments about this advisory:

Visit Wagtail's support channels Email us at security@wagtail.org (view our security policy for more information).

Affected Software

4 affected componentsFixes available
pip/wagtail=8.0rc1
8.0rc2
pip/wagtail>=7.4<7.4.3
7.4.3
pip/wagtail>=7.1<7.3.4
7.3.4
pip/wagtail<7.0.9
7.0.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/wagtail to a version that resolves this vulnerability.

    Fixed in 8.0rc2
  2. Upgrade

    Upgrade pip/wagtail to a version that resolves this vulnerability.

    Fixed in 7.4.3
  3. Upgrade

    Upgrade pip/wagtail to a version that resolves this vulnerability.

    Fixed in 7.3.4
  4. Upgrade

    Upgrade pip/wagtail to a version that resolves this vulnerability.

    Fixed in 7.0.9
  5. Upgrade

    Upgrade wagtail/wagtail to a version that resolves this vulnerability.

    Fixed in 7.0.9
  6. Upgrade

    Upgrade wagtail/wagtail to a version that resolves this vulnerability.

    Fixed in 7.3.4
  7. Upgrade

    Upgrade wagtail/wagtail to a version that resolves this vulnerability.

    Fixed in 7.4.3
  8. Upgrade

    Upgrade wagtail/wagtail to a version that resolves this vulnerability.

    Fixed in 8.0rc2

Event History

Aug 20, 2026
Advisory Published
via GitHub·06:45 PM
Data Sourced
via GitHub·06:45 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Wagtail deployments are exposed where a CMS user has "add" permission for a snippet model but lacks both "change" and "view" permission for snippets they may target. Such a user can copy an existing snippet they are not authorized to view.

2

What access does an attacker need?

An attacker needs an authenticated CMS account with "add" permission on the affected snippet model. No "change" or "view" permission is required for the snippet whose contents are disclosed.

3

Which Wagtail releases contain the fix?

The issue is patched in Wagtail 7.0.9, 7.3.4, 7.4.3, and 8.0rc2.

4

Is there a workaround if upgrading is not immediately possible?

No workaround is listed. Restrict or remove "add" permission for snippet models from users who should not be able to access existing snippet contents until a patched release can be deployed.

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