Plone Portlets Updates Fix Critical TALES Injection
Tech GuruQuick Answer
Plone CVE-2026-57149 permits server-side code execution by an authenticated user able to configure a Classic portlet. The default role map can include ordinary users managing their personal dashboards, so this is not limited to site administrators. Upgrade plone.app.portlets to the version appropriate for the Plone branch: 5.0.8 for Plone 6.0, 6.0.4 for 6.1, or 7.0.2 for 6.2.
Confirm Scope And Apply The Supported Fix
What to do now: inventory the package version, Classic portlet assignments and who can manage their own or shared portlets. While arranging the upgrade, follow the project's containment guidance to restrict untrusted portlet management and, where necessary, disable Classic portlet rendering. Preserve suspicious assignments as evidence without rendering them in production.
Source recheck: October 2, 2026 UTC. The linked project advisories were checked for this revision; deployment applicability and successful remediation still require local evidence. Recheck the supported release before changing production.
Scope And Authority
| Product scope | plone.app.portlets 5.0.0–5.0.7, 6.0.0–6.0.3, and 7.0.0–7.0.1 |
|---|---|
| Advisory | GHSA-rr49-f9g6-c9r5 |
| CVE | CVE-2026-57149 |
| Authoritative release date | 2026-06-23 UTC (project advisory dates, not database ingestion) |
| Authority revision date | 2026-06-24 UTC (project advisory dates, not database ingestion) |
| Affected versions | plone.app.portlets 5.0.0–5.0.7, 6.0.0–6.0.3, and 7.0.0–7.0.1 |
| Fixed version | Plone 6.0: plone.app.portlets 5.0.8.Plone 6.1: 6.0.4.Plone 6.2: 7.0.2. Use the branch-compatible supported package set, not a cross-branch pin chosen only by its higher number. |
| CVSS base score | 9.9 (CVSS v3.1) |
| CVSS severity | Critical |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Classic portlets construct a TALES expression from user-supplied template/macro fields. The vulnerable code interprets that value as an expression rather than only a path, crossing from a web user's configuration privileges into code execution as the Plone process. Restricting who can add a new portlet is not proof that an existing malicious assignment is inert; review stored assignments and the project's rendering-containment options as part of the response.
What To Validate Now
- Inventory. Record Plone and plone.app.portlets versions in every process, Classic portlet use, ManageOwnPortlets/Manage portlets grants and personal-dashboard configuration rights.
- Establish applicability. Compare each deployment with the authority's affected-version statement: plone.app.portlets 5.0.0–5.0.7, 6.0.0–6.0.3, and 7.0.0–7.0.1 Do not infer applicability from product family or severity alone.
- Remediate. Apply plone.app.portlets 5.0.8, 6.0.4, or 7.0.2 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Use staging and synthetic assignments to verify intended template/macro handling, authorized portlet management and ordinary rendering after upgrade. Do not execute a TALES code payload on the live site; review any suspected compromise separately from package remediation.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
