Plone.App.Textfield
Approved changes feed: RSS · Atom
cpe:2.3:a:plone:plone.app.textfield:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Plone (20065100-5fec-5b5e-bb46-a6d4673848e0) |
|---|---|
| Product | Plone.App.Textfield (301775f5-3317-522e-b6b3-829e89577c66) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-54503 |
vulnerable | 2026-09-16 04:33:28.542315 |
plone.app.textfield: Stored XSS by spoofing mime type
MEDIUM (4.3)
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.
Published: 2026-09-15T16:38:38.290Z
Updated: 2026-09-15T19:02:18.109Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.