CVE-2026-55247
moderateSSRF, DoS and Stored XSS in plone.app.event iCalendar Import
plone.app.event, the package that provides Plone's event content type, accepts insufficiently restricted calendar and event URLs in its iCalendar import (src/plone/app/event/ical/importer.py) in versions prior to 5.2.4 and 6.0.1. A logged-in editor can trigger an import with an attacker-chosen URL, causing the server to fetch internal network resources or local calendar files (SSRF), download an unbounded number of bytes and events, and commit work per event, which can exhaust server resources and take the site offline. The editor can also store a malicious event URL that executes script in another user's browser (stored XSS), consistent with the CVSS scope change. Any Plone deployment running plone.app.event 5.x before 5.2.4 or 6.x before 6.0.1, where editors can use the iCalendar import, is affected. No public proof-of-concept, CISA KEV listing, or known in-the-wild exploitation has been reported, and EPSS estimates roughly a 0.3% probability of exploitation within 30 days.
What to do: Upgrade plone.app.event to 5.2.4 on the 5.x branch or 6.0.1 on the 6.x branch, which restrict accepted URLs, enforce the MAXIMUM_ICAL_IMPORT_SIZE_BYTES and MAXIMUM_ICAL_IMPORT_EVENTS limits, use transaction savepoints, and validate event URLs. Until patched, restrict iCalendar import to trusted editors, apply egress filtering so the application server cannot reach internal services or local file URLs, and review stored event URLs for injected script.
| plone.app.event (5.x branch) | all versions prior to 5.2.4 |
| plone.app.event (6.x branch) | all versions prior to 6.0.1 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
plone.app.event provides the event content type for Plone. Prior to versions 5.2.4 and 6.0.1, the iCalendar import in src/plone/app/event/ical/importer.py accepts insufficiently restricted calendar and event URLs, does not adequately bound downloaded bytes or imported events, and commits work per event. A logged-in editor can make the server request internal network resources or local calendar files, exhaust resources and take the site offline, and store a malicious event URL that executes script in another user's browser. The fix restricts accepted URLs, applies MAXIMUM_ICAL_IMPORT_SIZE_BYTES and MAXIMUM_ICAL_IMPORT_EVENTS limits, uses transaction savepoints, and validates event URLs. This issue is fixed in versions 5.2.4 and 6.0.1.
- Weakness
- CWE-400
- Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
In the news0 stories
No ingested article mentions this CVE yet.