Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Plone XSS Vulnerability

CVE-2021-29002GHSA-38g6-x6jv-jwff

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

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

    Affected
    <= 5.2.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2021-29002: 0.76% estimated exploitation activity in the next 30 days; percentile 55.32 (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.

A stored cross-site scripting (XSS) vulnerability in Plone CMS 5.2.3 exists in site-controlpanel via the form.widgets.sitetitle parameter.

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

    Amended from ghsa record GHSA-38g6-x6jv-jwff

  2. Revision 1 · created ·

    Published from osv record GHSA-38g6-x6jv-jwff

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-2021-29002

Advisory: Plone XSS Vulnerability
IDs: CVE-2021-29002, GHSA-38g6-x6jv-jwff
Record: https://patchnext.com/advisories/cve-2021-29002 (revision 2, source checked 26 Oct 2026, 13:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI plone: affected <= 5.2.3

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on plone.
- 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://osv.dev/vulnerability/GHSA-38g6-x6jv-jwff (OSV record GHSA-38g6-x6jv-jwff lists affected ranges: PyPI plone >=0 <=5.2.3)
- Verified: https://github.com/advisories/GHSA-38g6-x6jv-jwff (GitHub-reviewed advisory GHSA-38g6-x6jv-jwff lists affected ranges: PyPI plone >=0 <=5.2.3)

Commands are suggestions: review each one before running it.

Loading voting…