Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Cross-site Scripting and Open Redirect in Products.ATContentTypes

CVE-2022-23599GHSA-g4c2-ghfg-g5rh

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (products-atcontenttypes 3.0.6), 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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2022-23599: 0.75% estimated exploitation activity in the next 30 days; percentile 54.99 (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 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 A new version 3.0.6 of Products.ATContentTypes has been released with a fix. This version works on Plone 5.2 (Python 2 only) and will be included in Plone 5.2.7. Note that the Products.CMFPlone package has the same problem in the 4.3 series. plone.app.contenttypes has the same problem in all versions, 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. Go to the 'Caching' control panel. If this does not exist, or…

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

    Amended from ghsa record GHSA-g4c2-ghfg-g5rh

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-g4c2-ghfg-g5rh

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-2022-23599

Advisory: Cross-site Scripting and Open Redirect in Products.ATContentTypes
IDs: CVE-2022-23599, GHSA-g4c2-ghfg-g5rh
Record: https://patchnext.com/advisories/cve-2022-23599 (revision 3, source checked 26 Oct 2026, 13:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: products-atcontenttypes 3.0.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI products-atcontenttypes: affected < 3.0.6; fixed in 3.0.6

## Suggested inspection (read-only)
- `python -m pip show products-atcontenttypes`: 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 products-atcontenttypes.
- 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-g4c2-ghfg-g5rh (OSV record GHSA-g4c2-ghfg-g5rh lists affected ranges: PyPI products-atcontenttypes >=0 <3.0.6 (fixed))
- Verified: https://github.com/advisories/GHSA-g4c2-ghfg-g5rh (GitHub-reviewed advisory GHSA-g4c2-ghfg-g5rh lists affected ranges: PyPI products-atcontenttypes >=0 <3.0.6)

Commands are suggestions: review each one before running it.

Loading voting…