plone-app-portlets
Affected
- introduced
7.0.0, fixed7.0.2(ecosystem)
Fixed versions
7.0.2
Fix
- Fixed version
7.0.2pip install --upgrade plone-app-portlets==7.0.2
Advisory
Also known as: CVE-2026-57149, PYSEC-2026-4138
plone.app.portlets Vulnerable to Remote Code Execution via TALES Injection
Impact
The Classic portlet (plone.app.portlets.portlets.classic) used its user-supplied template/macro fields to build a TALES path expression that was then evaluated by the TAL path() helper. Because the value was interpreted as a full TALES expression, a user able to add or edit a Classic portlet could supply a crafted value that escapes simple path traversal and is evaluated as arbitrary code.
This is exploitable by any authenticated user who can configure a Classic portlet - which, with the default role map, includes regular users on their personal dashboard. The result is code execution in the context of the Plone process, i.e. a privilege escalation across the trust boundary between an authenticated web user and the server-side process.
Patches
The problem has been patched in plone.app.portlets
plone.app.portlets 7.0.2.plone.app.portlets 6.0.4.plone.app.portlets 5.0.8.Workarounds
If upgrading is not immediately possible:
plone.app.portlets.ManageOwnPortlets permission from untrusted roles, and limit Manage portlets to trusted administrators (usually this is already restricted to the Manager and Site Administrator roles).portlets.xml in your own code, so it is not a quick fix.portal_view_customizations tool, locate the classic.pt template and click it. Click the Customize button. Remove all text and replace it with <div>The classic portlet was disabled.</div>. (This is not a recommended way of customising a template, but in this case it is quite effective.)Credits
Discovered by Giuseppe Caruso, and reported to the [Plone/Zope Security Team](mailto:[email protected]). Thanks!
Critical Basis: The source's own band: CRITICAL
7.0.0, fixed 7.0.2 (ecosystem)7.0.2
7.0.2pip install --upgrade plone-app-portlets==7.0.26.0.0, fixed 6.0.4 (ecosystem)6.0.4
6.0.4pip install --upgrade plone-app-portlets==6.0.45.0.0, fixed 5.0.8 (ecosystem)5.0.8
5.0.8pip install --upgrade plone-app-portlets==5.0.8Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0