CVE-2026-54503 | BDVDB-2026-373392 Detail
ploneplone.app.textfield
Description#
plone.app.textfield provides a zope.schema-style field type called RichText for storing a value with a related MIME type. Prior to 2.0.2, 3.0.2, and 4.0.1, depending on the release line, RichTextValue.output returns an unsanitized stored RichText value when mimeType equals outputMimeType, including values that claim the text/x-html-safe output type. This equality shortcut bypasses the safe_html transform even though the transform itself correctly removes event-handler attributes and unsafe URI schemes. Equal types can result from a RichText field configured with the same mimeType and outputMimeType or from REST API input that supplies text/x-html-safe as its content type. The raw stored value is then emitted through tal:content=structure without escaping, allowing a user who can set a RichText field to store JavaScript that executes in a viewer's browser. This issue is fixed in versions 2.0.2, 3.0.2, and 4.0.1.
Impact#
Per CVSS v3.1: confidentiality impact low, integrity impact none, availability impact none. Attack vector: network.
Weaknesses#
- CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
References#
- https://github.com/plone/plone.app.textfield/security/advisories/GHSA-4r4f-gg25-rmg5
- https://github.com/plone/plone.app.textfield/commit/0da1aeec2406cf640977eb857a03e792d2c7cac2
- https://github.com/plone/plone.app.textfield/commit/467638e500d804c637031387a227a2b02d12a86f
- https://github.com/plone/plone.app.textfield/commit/781d517a38524087fe57525a94806684908f852f
Exploit#
No public exploit known
History#
- Version 1Record published in the CVE List.