Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.9

plone.app.portlets Classic portlet lets users run code

CVE-2026-57149 · published 19 days ago
Summary

Versions of plone.app.portlets before the recent updates allow a user who can edit a Classic portlet to insert malicious code that the server will execute. This could let an ordinary user gain the same rights as the web application itself. Upgrade to the latest versions or limit portlet editing rights to trusted administrators to protect your site.

What to do
  • Update plone.app.portlets to version 7.0.2.
  • Update plone.app.portlets to version 6.0.4.
  • Update plone.app.portlets to version 5.0.8.
  • Update plone-app-portlets to version 7.0.2.
  • Update plone-app-portlets to version 6.0.4.
  • Update plone-app-portlets to version 5.0.8.
Affected software
Ecosystem VendorProductAffected versions
– plone plone.app.portlets >= 7.0.0, < 7.0.2
pip – plone.app.portlets >= 7.0.0, <= 7.0.1
>= 6.0.0, <= 6.0.3
>= 5.0.0, <= 5.0.7
Fix: upgrade to 7.0.2
PyPI – plone-app-portlets >= 7.0.0, < 7.0.2
>= 6.0.0, < 6.0.4
>= 5.0.0, < 5.0.8
Fix: upgrade to 7.0.2
Original advisory text
plone.app.portlets Vulnerable to Remote Code Execution via TALES Injection
plone.app.portlets.portlets provides a Plone-specific user interface for plone.portlets, as well as a standard set of portlets that ship with Plone. Starting in version 5.0.0 and prior to versions 5.0.8, 6.0.4, and 7.0.2, 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. The problem has been patched in `plone.app.portlets` 5.0.8, 6.0.4, and 7.0.2. Some workarounds are available. Restrict who can manage portlets: remove the `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). Where the Classic portlet is not needed, unregister it so it cannot be added. This would need to be done by editing a `portlets.xml` in your own code. One may also effectively disable showing the classic portlet by customising its template. In the Zope Management Interface go to the `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 customizing a template, but in this case it is quite effective.)
References
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
9.9 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-95Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Timeline
Published22 Sep 2026
Updated11 Oct 2026
First seen22 Sep 2026
Sources
CVE-2026-57149 · NVD
CVE-2026-57149 · MITRE
CVE-2026-57149 · OSV
GHSA-rr49-f9g6-c9r5 · GHSA
GHSA-rr49-f9g6-c9r5 · OSV
PYSEC-2026-4138 · OSV
Track software like this
Free during beta