Cross-site Scripting and Open Redirect in plone.app.contenttypes
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (plone-app-contenttypes 2.2.3), 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.
Affected packages
- Affected
- < 2.2.3
- Fixed in
- 2.2.3
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-f7qw-5fgj-247x lists affected ranges: PyPI plone-app-contenttypes >=0 <2.2.3 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-f7qw-5fgj-247x lists affected ranges: PyPI plone-app-contenttypes >=0 <2.2.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Impact Plone is vulnerable to reflected cross site scripting and open redirect when an attacker can get a compromised version of the imageviewfullscreen page in a cache, for example in Varnish. The technique is known as cache poisoning. Any later visitor can get redirected when clicking on a link on this page. Usually only anonymous users are affected, but this depends on your cache settings. Patches New versions of plone.app.contenttypes have been released. Version 2.2.3 works on Plone 5.2 and will be included in Plone 5.2.7. Version 3.0.0a9 works on Plone 6 and will be included in Plone 6.0.0a3. Note that the Products.CMFPlone package has the same problem in the 4.3 series. In Plone 5.0-5.2, the default Products.ATContentTypes version has the same problem. See advisory. For all unpatched versions of the three packages, you can use the following workaround. Workaround Make sure the imageviewfullscreen page is not stored in the cache. In Plone: Login as Manager and go to Site Setup.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-f7qw-5fgj-247x
- Revision 1 · created ·
Published from osv record GHSA-f7qw-5fgj-247x
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-f7qw-5fgj-247x Advisory: Cross-site Scripting and Open Redirect in plone.app.contenttypes IDs: GHSA-f7qw-5fgj-247x Record: https://patchnext.com/advisories/ghsa-f7qw-5fgj-247x (revision 2, source checked 26 Oct 2026, 13:08 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: plone-app-contenttypes 2.2.3. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI plone-app-contenttypes: affected < 2.2.3; fixed in 2.2.3 ## Suggested inspection (read-only) - `python -m pip show plone-app-contenttypes`: 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-contenttypes. - 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-f7qw-5fgj-247x (OSV record GHSA-f7qw-5fgj-247x lists affected ranges: PyPI plone-app-contenttypes >=0 <2.2.3 (fixed)) - Verified: https://github.com/advisories/GHSA-f7qw-5fgj-247x (GitHub-reviewed advisory GHSA-f7qw-5fgj-247x lists affected ranges: PyPI plone-app-contenttypes >=0 <2.2.3) Commands are suggestions: review each one before running it.
Loading voting…