PyPI · wagtail
Wagtail: Improper restriction handling on Pages admin API
The internal Pages admin API incorrectly returns page fields without access control when they are declared in api_fields. A user with access to the Wagtail admin can use this API to fetch draft and live page fields’ contents that are part of api_fields on the base page model (title, slug, seo_title, search_description), as well as all custom fields declared in api_fields.
The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.
Patched versions have been released as Wagtail 7.0.9, 7.3.4, 7.4.3 and 8.0rc2.
Site owners unable to upgrade can apply the fix by overriding the relevant method on PagesAdminAPIViewSet to patch all vulnerable admin API endpoints:
# wagtail_hooks.py or AppConfig.ready()
from wagtail.admin.api.views import PagesAdminAPIViewSet
from wagtail.permissions import page_permission_policy
def _restricted_get_base_queryset(self):
return page_permission_policy.explorable_instances(self.request.user)
PagesAdminAPIViewSet.get_base_queryset = _restricted_get_base_queryset
Many thanks to xuliang@QAX for reporting this issue.
If you have any questions or comments about this advisory:
Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.
Check my repoSources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.