High

Cross-Site Scripting in Wagtail

  • Disclosed: 20.07.2020
  • Updated: 11.10.2026 15:17

Impact

When a form page type is made available to Wagtail editors through the wagtail.contrib.forms app, and the page template is built using Django's standard form rendering helpers such as form.as_p (as directed in the documentation), any HTML tags used within a form field's help text will be rendered unescaped in the page. Allowing HTML within help text is an intentional design decision by Django; however, as a matter of policy Wagtail does not allow editors to insert arbitrary HTML by default, as this could potentially be used to carry out cross-site scripting attacks, including privilege escalation. This functionality should therefore not have been made available to editor-level users.

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

Patches

Patched versions have been released as Wagtail 2.7.4 (for the LTS 2.7 branch) and Wagtail 2.9.3 (for the current 2.9 branch). In these versions, help text will be escaped to prevent the inclusion of HTML tags. Site owners who wish to re-enable the use of HTML within help text (and are willing to accept the risk of this being exploited by editors) may set WAGTAILFORMS_HELP_TEXT_ALLOW_HTML = True in their configuration settings.

Workarounds

Site owners who are unable to upgrade to the new versions can secure their form page templates by rendering forms field-by-field as per Django's documentation, but omitting the |safe filter when outputting the help text.

Acknowledgements

Many thanks to Timothy Bautista for reporting this issue.

For more information

If you have any questions or comments about this advisory:

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) wagtail >= 2.8rc1, < 2.9.3, < 2.7.4 2.9.3, 2.7.4

References

CVSS score 5.7/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
Weakness (CWE)
CWE-79
Platform
Python (PyPI)
Package
wagtail
Disclosed
20.07.2020
Updated
11.10.2026 15:17

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2020-154 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-2473-9hgq-j7xw - CC BY 4.0

Vulnerability history: wagtail

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (30) in the archive
Total entries
30
First → latest
04.2020 08.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 5
  • Medium 22
  • Low 3

Disclosures per year

  1. 2020: 3
  2. 2021: 2
  3. 2022: 1
  4. 2023: 3
  5. 2024: 3
  6. 2025: 0
  7. 2026: 18
Severity:
  1. High · 7.3 CVE-2026-54263 >= 7.3, < 7.3.3, >= 7.4, < 7.4.2 7.3.3, 7.4.2
  2. High · 6.5 CVE-2024-39317 >= 6.0, < 6.0.6, >= 6.1, < 6.1.3, >= 2.0, < 5.2.6 6.0.6, 6.1.3, 5.2.6
  3. High · 6.4 CVE-2023-28836 >= 1.5, < 4.1.4, >= 4.2, < 4.2.2 4.1.4, 4.2.2
  4. High · 6.1 CVE-2021-29434 < 2.11.7, >= 2.12, < 2.12.4 2.11.7, 2.12.4
  5. Cross-Site Scripting in Wagtail this entry
    High · 5.7 CVE-2020-15118 >= 2.8rc1, < 2.9.3, < 2.7.4 2.9.3, 2.7.4

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.