Wagtail is an open source content management system built on Django. Prior to 7.0.9, 7.3.4, 7.4.3, and 8.0rc2, the Wagtail Documents and Images API V2 excludes directly restricted collections but fails to exclude their descendant collections, even though descendants inherit ancestor view restrictions. An API user can therefore list the filenames and names of documents and images stored in descendant collections that should remain private. This issue is fixed in versions 7.0.9, 7.3.4, 7.4.3, and 8.0rc2.

End of life: 5/4/2027, End of support: 2/2/2027, Latest version: 8.1

End of life: 2/2/2027, End of support: 11/3/2026, Latest version: 8.0.1

Impact A CMS user with the "submit translations" permission, could use the Admin API's "copy for translation" endpoint to copy an existing page that they do not have edit 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).

Impact

A reflected cross-site scripting (XSS) vulnerability exists on the dynamic image URL generator view within the Wagtail admin interface. A user with a limited-permission editor account for the Wagtail admin could craft a URL that, when viewed by a user with higher privileges, could perform actions with that user's credentials. The vulnerability is present for all sites, even if they do not enable the dynamic image serve view. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.

Patches

Patched versions have been released as Wagtail 7.3.3 and 7.4.2.

Workarounds

For sites that cannot easily upgrade to a current supported version, the vulnerability can be patched by adding the following code to urls.py URL pattern declarations to override the vulnerable view. This disables the admin dynamic image preview functionality, while the public-facing dynamic image serve view still works.

python from django.http import HttpResponseBadRequest from django.urls import path from wagtail.admin import urls as wagtailadminurls

def disabledoutput(request, imageid): return HttpResponseBadRequest("", contenttype="text/plain")

urlpatterns = [ # Example where the CMS admin is at /admin/. # Add this before the Wagtail admin URLs registration, with the same sub-path. path("admin/images/<int:imageid>/generateurl/output/", disabledoutput), path("admin/", include(wagtailadminurls)), ]

Acknowledgements

Many thanks to Thibaud Colas (@thibaudcolas) 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).

Impact A low-level user with the "Can submit translation" permission can create translations for any page, including those they do not have permissions for.

Patches Patched versions have been released as Wagtail 7.0.8, 7.3.3, 7.4.2.

Workarounds N/A

Acknowledgements

Many thanks to @devansh3008 and @alanturing881 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).

Impact Due to a missing permission check on the image preview endpoint, a user with access to the Wagtail admin can preview any image. The existing data of the image object itself is not exposed. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.

Patches Patched versions have been released as Wagtail 7.0.8, 7.3.3, 7.4.2.

Workarounds For sites that cannot easily upgrade to a current supported version, the vulnerability can be patched by adding the following code to urls.py URL pattern declarations to override the vulnerable view.

python from django.core.exceptions import PermissionDenied from django.shortcuts import getobjector404 from django.urls import path from wagtail.admin import urls as wagtailadminurls from wagtail.images.permissions import permissionpolicy from wagtail.images.views import preview

def patchedpreview(request, imageid, filterspec): image = getobjector404(getimagemodel(), id=imageid)

if not permissionpolicy.userhaspermissionforinstance(request.user, "change", image): raise PermissionDenied

return preview(request, imageid, filterspec)

urlpatterns = [ # Example where the CMS admin is at /admin/. # Add this before the Wagtail admin URLs registration, with the same sub-path. path("admin/images/<int:imageid>/preview/<str:filterspec>/", patchedpreview) path("admin/", include(wagtailadminurls)), ]

Acknowledgements Many thanks to @0x1saac and @harshakshit 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).

Impact The Documents and Images chooser's chosen endpoint incorrectly listed items for which the user has not been granted choose permission. A user with access to the Wagtail admin could see the filename and name and URLs of documents and images in those collections.

The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.

Patches Patched versions have been released as Wagtail 7.0.8, 7.3.3, 7.4.2.

Workarounds N/A

Acknowledgements Many thanks to @harshakshit 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).

Impact

An authenticated admin user can trigger expensive rendition processing with purposefully crafted filter specs resulting in potentially service degradation.

The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.

Patches Patched versions have been released as Wagtail 7.0.8, 7.3.3, 7.4.2.

Workarounds For sites that cannot easily upgrade to a current supported version, the vulnerability can be patched by adding the following code to urls.py URL pattern declarations to override the vulnerable view.

python from django.core.exceptions import PermissionDenied from django.http import HttpResponseBadRequest from django.shortcuts import getobjector404 from django.urls import path from wagtail.admin import urls as wagtailadminurls from wagtail.images.exceptions import InvalidFilterSpecError from wagtail.images.permissions import permissionpolicy from wagtail.images.views import preview

def patchedpreview(request, imageid, filterspec): image = getobjector404(getimagemodel(), id=imageid)

if not permissionpolicy.userhaspermissionforinstance(request.user, "change", image): raise PermissionDenied

try: filterobj = Filter(spec=filterspec) except InvalidFilterSpecError: return HttpResponseBadRequest("Invalid filter spec", contenttype="text/plain")

allowed = {"original", "width", "height", "min", "max", "fill"} if any(operation.method not in allowed for operation in filterobj.operations): return HttpResponseBadRequest("Invalid filter spec", contenttype="text/plain")

return preview(request, imageid, filterspec)

urlpatterns = [ # Example where the CMS admin is at /admin/. # Add this before the Wagtail admin URLs registration, with the same sub-path. path("admin/images/<int:imageid>/preview/<str:filterspec>/", patchedpreview) path("admin/", include(wagtailadminurls)), ]

Acknowledgements Many thanks to @0x1saac 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).

End of life: 11/2/2027, End of support: 11/2/2027, Latest version: 7.4.4

End of life: 8/25/2026, End of support: 5/4/2026, Latest version: 7.3.4

End of life: 5/4/2026, End of support: 2/2/2026, Latest version: 7.2.3

End of life: 2/2/2026, End of support: 11/5/2025, Latest version: 7.1.3

Wagtail CMS 6.4.1 is vulnerable to a Stored Cross-Site Scripting (XSS) in the document upload functionality. Attackers can inject malicious code inside a PDF file. When a user clicks the document in the CMS interface, the payload executes. NOTE: this is disputed by the Supplier because "It has been well documented that when serving uploaded files using a method outside of Wagtail (which admittedly is the default), it requires additional configuration from the developer, because Wagtail cannot control how these are served. ... For example, if a Wagtail instance is configured to upload files into AWS S3, Wagtail cannot control the permissions on how they're served, nor any headers used when serving them (a limitation of S3)."

End of life: 11/2/2026, End of support: 11/2/2026, Latest version: 7.0.10

End of life: 8/4/2025, End of support: 5/6/2025, Latest version: 6.4.2

End of life: 5/6/2025, End of support: 5/6/2025, Latest version: 5.2.8

End of life: 5/6/2025, End of support: 5/6/2025, Latest version: 5.2.8

End of life: 5/1/2026, End of support: 5/1/2026, Latest version: 6.3.8

End of life: 5/1/2026, End of support: 5/1/2026, Latest version: 6.3.8

End of life: 2/3/2025, End of support: 11/1/2024, Latest version: 6.2.4

End of life: 2/3/2025, End of support: 11/1/2024, Latest version: 6.2.4

Impact

A bug in Wagtail's parsequerystring would result in it taking a long time to process suitably crafted inputs. When used to parse sufficiently long strings of characters without a space, parsequerystring would take an unexpectedly large amount of time to process, resulting in a denial of service.

In an initial Wagtail installation, the vulnerability can be exploited by any Wagtail admin user. It cannot be exploited by end users. If your Wagtail site has a custom search implementation which uses parsequerystring, it may be exploitable by other users (e.g. unauthenticated users).

Patches

Patched versions have been released as Wagtail 5.2.6, 6.0.6 and 6.1.3.

This vulnerability affects all unpatched versions from Wagtail 2.0 onwards.

Workarounds

Site owners who are unable to upgrade to a patched version can limit the length of search terms passed to parsequerystring. Whilst the performance characteristics will depend on your hosting environment, 1000 characters has been shown to still be fairly fast, without triggering this vulnerability.

No workaround is available for the Wagtail admin usage.

Acknowledgements

Many thanks to Jake Howard 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).

End of life: 11/1/2024, End of support: 8/1/2024, Latest version: 6.1.3

End of life: 11/1/2024, End of support: 8/1/2024, Latest version: 6.1.3

End of life: 8/1/2024, End of support: 5/1/2024, Latest version: 6.0.6

End of life: 8/1/2024, End of support: 5/1/2024, Latest version: 6.0.6

Impact

A user with a limited-permission editor account for the Wagtail admin can make a direct URL request to the admin view that handles bulk actions on user accounts. While authentication rules prevent the user from making any changes, the error message discloses the display names of user accounts, and by modifying URL parameters, the user can retrieve the display name for any user. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.

Patches Patched versions have been released as Wagtail 4.1.9 (LTS), 5.0.5 and 5.1.3. The fix is also included in Release Candidate 1 of the forthcoming Wagtail 5.2 release.

Workarounds None.

Acknowledgements Many thanks to @quyenheu 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).

End of life: 2/1/2024, End of support: 11/1/2023, Latest version: 5.1.3

End of life: 2/1/2024, End of support: 11/1/2023, Latest version: 5.1.3