GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-X5G3-W747-2H8Q

Vulnerability from github – Published: 2026-08-28 18:41 – Updated: 2026-08-28 18:41
VLAI
Summary
plone.app.portlets vulnerable to denial of service via RSS feed portlet
Details

Impact

By adding an RSS portlet, and giving this a link to a very large file, a member can cause a denial of service attack, because Plone will use lots of memory. The member could also use different urls to try to get information about the internal network and open port numbers (SSRF). A malicious RSS feed could cause stored XSS, when the url of a feed item is a javascript url.

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 not immediately possible:

  • 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 RSS 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, so it is not a quick fix.

References

This is similar to this plone.app.event vulnerability. It was discovered by the Plone Security Team by thinking of similar cases to the plone.app.event problem.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 7.0.1"
      },
      "package": {
        "ecosystem": "PyPI",
        "name": "plone.app.portlets"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "7.0.0"
            },
            {
              "fixed": "7.0.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "plone.app.portlets"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.0.0"
            },
            {
              "fixed": "6.0.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "plone.app.portlets"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.0.8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-55248"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-08-28T18:41:35Z",
    "nvd_published_at": null,
    "severity": "CRITICAL"
  },
  "details": "### Impact\nBy adding an RSS portlet, and giving this a link to a very large file, a member can cause a denial of service attack, because Plone will use lots of memory. The member could also use different urls to try to get information about the internal network and open port numbers (SSRF). A malicious RSS feed could cause stored XSS, when the url of a feed item is a javascript url.\n\n### Patches\nThe problem has been patched in `plone.app.portlets`.\n\n* For Plone 6.2: upgrade to `plone.app.portlets` 7.0.2\n* For Plone 6.1: upgrade to `plone.app.portlets` 6.0.4\n* For Plone 6.0: upgrade to `plone.app.portlets` 5.0.8\n\n### Workarounds\nIf upgrading is not immediately possible:\n\n- 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).\n- Where the RSS 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, so it is not a quick fix.\n\n### References\n\nThis is similar to this [`plone.app.event` vulnerability](https://github.com/plone/plone.app.event/security/advisories/GHSA-r82h-mqw3-fc56). It was discovered by the Plone Security Team by thinking of similar cases to the `plone.app.event` problem.",
  "id": "GHSA-x5g3-w747-2h8q",
  "modified": "2026-08-28T18:41:35Z",
  "published": "2026-08-28T18:41:35Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/plone/plone.app.portlets/security/advisories/GHSA-x5g3-w747-2h8q"
    },
    {
      "type": "WEB",
      "url": "https://github.com/plone/plone.app.portlets/commit/09da52ef7b297daa8e0cfd2361e47c37d9b073ad"
    },
    {
      "type": "WEB",
      "url": "https://github.com/plone/plone.app.portlets/commit/9f16b6fb10211916686c6c346ea174bf517e3fbd"
    },
    {
      "type": "WEB",
      "url": "https://github.com/plone/plone.app.portlets/commit/a3b2c2887165b308cd915cbb87b8276f90a76680"
    },
    {
      "type": "WEB",
      "url": "https://github.com/plone/plone.app.portlets/commit/df5e256baee55083cbd6b9a2623675d4cb26b6cd"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/plone/plone.app.portlets"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "plone.app.portlets vulnerable to denial of service via RSS feed portlet"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…