Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.9amended

plone.app.portlets Vulnerable to Remote Code Execution via TALES Injection

CVE-2026-57149GHSA-rr49-f9g6-c9r5

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (plone-app-portlets 7.0.2, 6.0.4, 5.0.8), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI plone-app-portlets

    Affected
    >= 7.0.0, <= 7.0.1>= 6.0.0, <= 6.0.3>= 5.0.0, <= 5.0.7
    Fixed in
    5.0.8, 7.0.2, 6.0.4

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-57149: 0.64% estimated exploitation activity in the next 30 days; percentile 50.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 For Plone 6.2, upgrade to plone.app.portlets 7.0.2. For Plone 6.1, upgrade to plone.app.portlets 6.0.4. For Plone 6.0, upgrade to plone.app.portlets 5.0.8. Workarounds If upgrading is…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-rr49-f9g6-c9r5

  2. Revision 2 · amended ·

    Amended from osv record GHSA-rr49-f9g6-c9r5

  3. Revision 1 · created ·

    Published from ghsa record GHSA-rr49-f9g6-c9r5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-57149

Advisory: plone.app.portlets Vulnerable to Remote Code Execution via TALES Injection
IDs: CVE-2026-57149, GHSA-rr49-f9g6-c9r5
Record: https://patchnext.com/advisories/cve-2026-57149 (revision 3, source checked 26 Oct 2026, 13:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: plone-app-portlets 7.0.2, 6.0.4, 5.0.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI plone-app-portlets: affected >= 7.0.0, <= 7.0.1; >= 6.0.0, <= 6.0.3; >= 5.0.0, <= 5.0.7; fixed in 5.0.8, 7.0.2, 6.0.4

## Suggested inspection (read-only)
- `python -m pip show plone-app-portlets`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on plone-app-portlets.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rr49-f9g6-c9r5 (GitHub-reviewed advisory GHSA-rr49-f9g6-c9r5 lists affected ranges: PyPI plone-app-portlets >=7.0.0 =6.0.0 =5.0.0 <=5.0.7)
- Verified: https://osv.dev/vulnerability/GHSA-rr49-f9g6-c9r5 (OSV record GHSA-rr49-f9g6-c9r5 lists affected ranges: PyPI plone-app-portlets >=7.0.0 =6.0.0 =5.0.0 <5.0.8 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…