plone-app-textfield
Affected
- introduced
0, fixed2.0.2(ecosystem)
Fixed versions
2.0.2
Fix
- Fixed version
2.0.2pip install --upgrade plone-app-textfield==2.0.2
Advisory
Also known as: CVE-2026-54503, PYSEC-2026-3497
plone.app.textfield: Stored XSS by spoofing mime type
Impact
A stored XSS affecting RichText fields. RichTextValue.output returns the raw, unsanitized stored value whenever the stored mimeType equals the outputMimeType. Because the safe-HTML output type (text/x-html-safe) is the type that signifies "already sanitized", any value whose stored mimeType equals it bypasses the safe_html transform entirely on render. The transform itself is sound — it correctly strips on* event-handler attributes and javascript:/data: URIs; the defect is that it is never invoked for these values. The unsanitized value is then emitted via tal:content="structure ...", which performs no escaping, so the payload executes in the viewer's browser.
This can be a problem when a RichText field is wrongly defined in code with a mimeType and outputMimeType that are the same, or when the REST API is used to the same effect.
Patches
The problem has been patched:
plone.app.textfield to 2.0.2.plone.app.textfield to 3.0.2.plone.app.textfield to 4.0.1.Workarounds
There is no known workaround.
Medium Basis: The source's own band: MODERATE
0, fixed 2.0.2 (ecosystem)2.0.2
2.0.2pip install --upgrade plone-app-textfield==2.0.23.0.0, fixed 3.0.2 (ecosystem)3.0.2
3.0.2pip install --upgrade plone-app-textfield==3.0.24.0.0, fixed 4.0.1 (ecosystem)4.0.1
4.0.1pip install --upgrade plone-app-textfield==4.0.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0