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 stored Cross-site Scripting (XSS) vulnerability exists on confirmation messages within the wagtail.contrib.simpletranslation module. A user with access to the Wagtail admin area may create a page with a specially-crafted title which, when another user performs the "Translate" action, causes arbitrary JavaScript code to run. This could lead to performing actions with that user's credentials. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.
Patches Patched versions have been released as Wagtail 6.3.8, 7.0.6, 7.2.3 and 7.3.1.
Workarounds None
Acknowledgements
Many thanks to Guan Chenxian (@GCXWLP) for reporting this issue.
For more information
If there are any questions or comments about this advisory:
- Visit Wagtail's support channels - Email Wagtail at security@wagtail.org (view the security policy for more information).
Impact A stored Cross-site Scripting (XSS) vulnerability exists on rendering TableBlock blocks within a StreamField. A user with access to create or edit pages containing TableBlock StreamField blocks is able to set specially-crafted class attributes on the block which run arbitrary JavaScript code when the page is viewed. When viewed by a user with higher privileges, this could lead to performing actions with that user's credentials. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin, and only affects sites using TableBlock.
Patches Patched versions have been released as Wagtail 6.3.8, 7.0.6, 7.2.3 and 7.3.1.
Workarounds Site owners who are unable to upgrade to the new versions can remediate the vulnerability by setting a template attribute on all TableBlock definitions, referencing a template that does not output class attributes. For example:
django <!-- For use with TableBlock(template="path/to/tableblock.html") --> <table> {% if tablecaption %} <caption>{{ tablecaption }}</caption> {% endif %} {% if tableheader %} <thead> <tr> {% for cell in tableheader %} <th scope="col">{{ cell }}</th> {% endfor %} </tr> </thead> {% endif %} <tbody> {% for row in data %} <tr> {% for cell in row %} {% if firstcolisheader and forloop.first %} <th scope="row">{{ cell }}</th> {% else %} <td>{{ cell }}</td> {% endif %} {% endfor %} </tr> {% endfor %} </tbody> </table>
Acknowledgements
Many thanks to Guan Chenxian (@GCXWLP) for reporting this issue.
For more information
If there are any questions or comments about this advisory:
- Visit Wagtail's support channels - Email Wagtail at security@wagtail.org (view the security policy for more information).