Answer in brief
CVE-2026-54503 records a Medium severity vulnerability in plone.app.textfield: Stored XSS by spoofing mime type. The current sources do not mark it as known exploited. The current feed maps plone/plone.app.textfield (generic), plone.app.textfield (pip), plone.app.textfield (pip), plone.app.textfield (pip). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps plone/plone.app.textfield (generic), plone.app.textfield (pip), plone.app.textfield (pip), plone.app.textfield (pip). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| plone/plone.app.textfieldgeneric | < 2.0.2 || >= 3.0.0, < 3.0.2 || >= 4.0.0, < 4.0.1 | Not reported |
| plone.app.textfieldpip | <2.0.2 | 2.0.2 |
| plone.app.textfieldpip | >=3.0.0,<3.0.2 | 3.0.2 |
| plone.app.textfieldpip | =4.0.0 | 4.0.1 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.