Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
2.7
CVE-2024-32882: Wagtail lets editors change fields they shouldn't
CVE-2024-32882 · published 2 years ago
Summary
In certain versions of Wagtail, if a content model is set up with field-level restrictions, an editor who can normally edit the model could still change those restricted fields by sending a crafted request. This only affects users who already have edit access to the model, not regular site visitors. Upgrade to Wagtail 6.0.3 or later, or redesign the model to separate restricted fields, to eliminate the risk.
What to do
- Update wagtail core team + contributors wagtail to version 6.0.3.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| pip | wagtail core team + contributors | wagtail |
>= 6.0.0, < 6.0.3 Fix: upgrade to 6.0.3
|
Original advisory text
Permission check bypass when editing a model with per-field restrictions in wagtail
Wagtail is an open source content management system built on Django. In affected versions if a model has been made available for editing through the `wagtail.contrib.settings` module or `ModelViewSet`, and the `permission` argument on `FieldPanel` has been used to further restrict access to one or more fields of the model, a user with edit permission over the model but not the specific field can craft an HTTP POST request that bypasses the permission check on the individual field, allowing them to update its value. This vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin, or by a user who has not been granted edit access to the model in question. The editing interfaces for pages and snippets are also unaffected. Patched versions have been released as Wagtail 6.0.3 and 6.1. Wagtail releases prior to 6.0 are unaffected. Users are advised to upgrade. Site owners who are unable to upgrade to a patched version can avoid the vulnerability as follows: 1.For models registered through `ModelViewSet`, register the model as a snippet instead; 2. For settings models, place the restricted fields in a separate settings model, and configure permission at the model level.
References
- https://github.com/wagtail/wagtail/commit/fa0d4829f9c81eefb37cc058e2fa1b6a918741...
- https://github.com/wagtail/wagtail/releases/tag/v6.0.3
- https://github.com/advisories/GHSA-w2v8-php4-p8hc
- https://docs.wagtail.org/en/stable/extending/generic_views.html#modelviewset URL
- https://docs.wagtail.org/en/stable/reference/contrib/settings.html URL
- https://docs.wagtail.org/en/stable/reference/pages/panels.html#wagtail.admin.pan... URL
- https://github.com/wagtail/wagtail/security/advisories/GHSA-w2v8-php4-p8hc Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2024-32882 Vendor Advisory
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/32xxx/CVE-2024-32882... Vendor Advisory
- https://github.com/wagtail/wagtail/commit/ab2a5d82b4ee3c909d2456704388ccf90e367c... Patch
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Type
CWE-280Improper Handling of Insufficient Permissions or Privileges
CWE-281Improper Preservation of Permissions
Timeline
Published2 May 2024
Updated4 Nov 2026
First seen6 Mar 2026
Track software like this
Free during beta