CVE-2026-54503

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-78836 (ENISA EUVD) · GHSA-4r4f-gg25-rmg5 (GitHub Security Advisories)Source: ENISA EUVD

4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 17, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_commit.
GitHub commit

commit 781d517a3852 (plone/plone.app.textfield)

Fix landed in plone/plone.app.textfield commit 781d517a3852 — awaiting tagged release

https://github.com/plone/plone.app.textfield/commit/781d517a38524087fe57525a94806684908f852f
GitHub commit

commit 467638e500d8 (plone/plone.app.textfield)

Fix landed in plone/plone.app.textfield commit 467638e500d8 — awaiting tagged release

https://github.com/plone/plone.app.textfield/commit/467638e500d804c637031387a227a2b02d12a86f
GitHub commit

commit 0da1aeec2406 (plone/plone.app.textfield)

Fix landed in plone/plone.app.textfield commit 0da1aeec2406 — awaiting tagged release

https://github.com/plone/plone.app.textfield/commit/0da1aeec2406cf640977eb857a03e792d2c7cac2
GitHub advisoryMentions a patch (unverified)

Stored XSS by spoofing mime type · Advisory · plone/plone.app.textfield · GitHub

https://github.com/plone/plone.app.textfield/security/advisories/GHSA-4r4f-gg25-rmg5

Vendor Advisories for CVE-2026-54503(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
plone-app-textfield1.0 ... 4.0.0 (37 versions)
  • every version up to 2.0.2: fixed in 2.0.2
  • 3.0.0 up to 3.0.2: fixed in 3.0.2
  • 4.0.0 up to 4.0.1: fixed in 4.0.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-25 14:19 UTCEG score recompute
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-22 21:20 UTCEG score recompute
  8. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-18 03:30 UTCEG score recompute
  14. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-10-12 15:56 UTCEG score recompute
  21. 2026-10-11 19:39 UTCEG score recompute
  22. 2026-10-11 16:54 UTCEG score recompute
  23. 2026-10-11 14:18 UTCEG score recompute
  24. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Show 32 more
  1. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-09-30 17:52 UTCEG score recompute
  11. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-09-28 07:52 UTCEG score recompute
  14. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-09-24 04:34 UTCEG score recompute
  18. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-09-23 02:25 UTCEG score recompute
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-09-18 11:02 UTCEG score recompute
  23. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-09-17 10:15 UTCEG score recompute
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  26. 2026-09-15 19:41 UTCEG score recompute
  27. 2026-09-15 19:14 UTCEG score recompute
  28. 2026-09-15 17:34 UTCEG score recompute
  29. 2026-07-30 14:22 UTCEG score recompute
  30. 2026-07-26 11:18 UTCEG score recompute
  31. 2026-07-23 03:19 UTCEG score recompute
  32. 2026-07-17 19:00 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54503?
CVE-2026-54503 is a medium-severity vulnerability; its CVE record was published on July 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…
When was the CVE record for CVE-2026-54503 published?
The CVE record for CVE-2026-54503 was published on July 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-54503 actively exploited?
CVE-2026-54503 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54503?
CVE-2026-54503 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54503?
A fix for CVE-2026-54503 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54503 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54503

Explore →

Is Your Infrastructure Affected by CVE-2026-54503?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs