Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact By abusing the iCalendar import functionality, a logged-in editor could take the whole site offline, make the server reach into the internal network and read calendar files off disk (SSRF), and store XSS. Patches The problem has been patched in plone.app.event. For Plone 6.2: upgrade to plone.app.event 6.0.1 For Plone 6.1: upgrade to plone.app.event 5.2.4 For Plone 6.0: upgrade to plone.app.event 5.2.4 Workarounds In the site root, go to the Security tab of the Zope Management Interface (manageaccess), look for the "plone.app.event: Import Ical" permission, and grant this only to the Manager role. Then only users with the Manager role can use the ical import form. There is no workaround for the stored XSS in the URL field of events. The vulnerabilities were discovered by Timothy Dudley and responsibly reported to the Plone Security Team. Thank you!
Recommended action: Upgrade to 6.0.1 or 5.2.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Plone before 5.2.3 allows XXE attacks via a feature that is protected by an unapplied permission of plone.schemaeditor.ManageSchemata (therefore, only available to the Manager role).
Recommended action: Upgrade to 3.2.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Plone before 5.2.3 allows SSRF attacks via the tracebacks feature (only available to the Manager role).
Recommended action: Upgrade to 3.2.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Plone before 5.2.3 allows XXE attacks via a feature that is explicitly only available to the Manager role.
Recommended action: Upgrade to 3.2.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.