Ecosyste.ms: Advisories
An open API service providing security vulnerability metadata for many open source software ecosystems.
Security Advisories: MDE2OlNlY3VyaXR5QWR2aXNvcnlHSFNBLXhmcnctaHhyNS1naHFm
Cross-site Scripting in wagtail
Impact
When the {% include_block %}
template tag is used to output the value of a plain-text StreamField block (CharBlock
, TextBlock
or a similar user-defined block derived from FieldBlock
), and that block does not specify a template for rendering, the tag output is not properly escaped as HTML. This could allow users to insert arbitrary HTML or scripting. This vulnerability is only exploitable by users with the ability to author StreamField content (i.e. users with 'editor' access to the Wagtail admin).
Patches
Patched versions have been released as Wagtail 2.11.8 (for the LTS 2.11 branch), Wagtail 2.12.5, and Wagtail 2.13.2 (for the current 2.13 branch).
Site implementors who wish to retain the existing behaviour of allowing editors to insert HTML content in these blocks (and are willing to accept the risk of untrusted editors inserting arbitrary code) may disable the escaping by surrounding the relevant {% include_block %}
tag in {% autoescape off %}...{% endautoescape %}
.
Workarounds
Site implementors who are unable to upgrade to a current supported version should audit their use of {% include_block %}
to ensure it is not used to output CharBlock
/ TextBlock
values with no associated template. Note that this only applies where {% include_block %}
is used directly on that block (uses of include_block
on a block containing a CharBlock / TextBlock, such as a StructBlock, are unaffected). In these cases, the tag can be replaced with Django's {{ ... }}
syntax - e.g. {% include_block my_title_block %}
becomes {{ my_title_block }}
.
Acknowledgements
Many thanks to Karen Tracey 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 [email protected] (if you wish to send encrypted email, the public key ID is
0x6ba1e1a86e0f8ce8
)
JSON: https://advisories.ecosyste.ms/api/v1/advisories/MDE2OlNlY3VyaXR5QWR2aXNvcnlHSFNBLXhmcnctaHhyNS1naHFm
Source: GitHub Advisory Database
Origin: Unspecified
Severity: Moderate
Classification: General
Published: almost 3 years ago
Updated: about 1 year ago
CVSS Score: 5.4
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Identifiers: GHSA-xfrw-hxr5-ghqf, CVE-2021-32681
References:
- https://github.com/wagtail/wagtail/security/advisories/GHSA-xfrw-hxr5-ghqf
- https://nvd.nist.gov/vuln/detail/CVE-2021-32681
- https://github.com/wagtail/wagtail/releases/tag/v2.11.8
- https://github.com/wagtail/wagtail/releases/tag/v2.12.5
- https://github.com/wagtail/wagtail/releases/tag/v2.13.2
- https://github.com/advisories/GHSA-xfrw-hxr5-ghqf
Blast Radius: 17.8
Affected Packages
pypi:wagtail
Dependent packages: 177Dependent repositories: 1,955
Downloads: 233,839 last month
Affected Version Ranges: >= 2.13, < 2.13.2, >= 2.12, < 2.12.5, < 2.11.8
Fixed in: 2.13.2, 2.12.5, 2.11.8
All affected versions: 0.3.1, 0.4.1, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.8.5, 0.8.6, 0.8.7, 0.8.8, 0.8.9, 0.8.10, 1.3.1, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.5.1, 1.5.2, 1.5.3, 1.6.1, 1.6.2, 1.6.3, 1.8.1, 1.8.2, 1.9.1, 1.10.1, 1.11.1, 1.12.1, 1.12.2, 1.12.3, 1.12.4, 1.12.5, 1.12.6, 1.13.1, 1.13.2, 1.13.3, 1.13.4, 2.0.1, 2.0.2, 2.1.1, 2.1.2, 2.1.3, 2.2.1, 2.2.2, 2.5.1, 2.5.2, 2.6.1, 2.6.2, 2.6.3, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.8.1, 2.8.2, 2.9.1, 2.9.2, 2.9.3, 2.10.1, 2.10.2, 2.11.1, 2.11.2, 2.11.3, 2.11.4, 2.11.5, 2.11.6, 2.11.7, 2.12.1, 2.12.2, 2.12.3, 2.12.4, 2.13.1
All unaffected versions: 2.11.8, 2.11.9, 2.12.5, 2.12.6, 2.13.2, 2.13.3, 2.13.4, 2.13.5, 2.14.1, 2.14.2, 2.15.1, 2.15.2, 2.15.3, 2.15.4, 2.15.5, 2.15.6, 2.16.1, 2.16.2, 2.16.3, 3.0.1, 3.0.2, 3.0.3, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.1.7, 4.1.8, 4.1.9, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.1.1, 5.1.2, 5.1.3, 5.2.1, 5.2.2, 5.2.3, 5.2.4, 6.0.1, 6.0.2