cve.bz

CVE-2021-32681 torchbox wagtail: Cross-site Scripting

5.4 mediumExploit referenceEPSS 1.1%Fix available

Medium (5.4) in torchbox wagtail. EPSS 1.1% estimated probability of exploitation activity in the next 30 days. Fixed in wagtail 2.11.8, 2.12.5, 2.13.2.

On this page
Wagtail is an open source content management system built on Django. A cross-site scripting vulnerability exists in versions 2.13-2.13.1, versions 2.12-2.12.4, and versions prior to 2.11.8. 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). 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). As a workaround, 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 }}`.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 67th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • wagtail (PyPI): fixed in 2.11.8, 2.12.5, 2.13.2

Ask an AI about this CVE

Show the promptExplain CVE-2021-32681 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-32681?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-32681?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-32681 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
torchbox:wagtailbefore 2.11.8
torchbox:wagtailfrom 2.12 through 2.12.4
torchbox:wagtailfrom 2.13 through 2.13.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xfrw-hxr5-ghqfPyPIwagtail<2.11.82.11.8
GHSA-xfrw-hxr5-ghqfPyPIwagtail>=2.12 <2.12.52.12.5
GHSA-xfrw-hxr5-ghqfPyPIwagtail>=2.13 <2.13.22.13.2
PYSEC-2021-103PyPIwagtail<2.11.8
>=2.12 <2.12.5
>=2.13 <2.13.2
2.11.8, 2.12.5, 2.13.2

Attack patterns (CAPEC)

  • CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
  • CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
  • CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
  • CAPEC-592 Stored XSS Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON