Skip to content
OpenAdvisories
Medium · 4.3 CVE-2026-54503 EUVD-2026-78836GHSA-4r4f-gg25-rmg5PYSEC-2026-3497

plone.app.textfield: Stored XSS by spoofing mime type

Published Sep 15, 2026 · Updated Sep 15, 2026 · Assigned by GitHub_M

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.

Affected products

VendorProductAffectedFixed
plone plone.app.textfield < 2.0.2, >= 3.0.0, < 3.0.2, >= 4.0.0, < 4.0.1 —

Affected packages

EcosystemPackageAffectedFixedRecord
PyPI plone-app-textfield < 2.0.2 2.0.2 GHSA-4r4f-gg25-rmg5
PyPI plone-app-textfield >= 3.0.0, < 3.0.2 3.0.2 GHSA-4r4f-gg25-rmg5
PyPI plone-app-textfield >= 4.0.0, < 4.0.1 4.0.1 GHSA-4r4f-gg25-rmg5
PyPI plone-app-textfield < 2.0.2 · >= 3.0.0, < 3.0.2 · >= 4.0.0, < 4.0.1 2.0.2, 3.0.2, 4.0.1 PYSEC-2026-3497

References