How severe is GHSA-g4c2-ghfg-g5rh?

GHSA-g4c2-ghfg-g5rh has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-g4c2-ghfg-g5rh?

GHSA-g4c2-ghfg-g5rh affects the following packages: products-atcontenttypes (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-g4c2-ghfg-g5rh?

Update products-atcontenttypes to 3.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g4c2-ghfg-g5rh is resolved across your whole dependency graph.

How do I detect GHSA-g4c2-ghfg-g5rh in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for products-atcontenttypes. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-g4c2-ghfg-g5rh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-g4c2-ghfg-g5rh?

O3 pinpoints whether GHSA-g4c2-ghfg-g5rh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-g4c2-ghfg-g5rh actively exploited in the wild?

No public exploit code has been indexed for GHSA-g4c2-ghfg-g5rh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-g4c2-ghfg-g5rh?

GHSA-g4c2-ghfg-g5rh has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g4c2-ghfg-g5rh?

GHSA-g4c2-ghfg-g5rh is classified as Cross-site Scripting (XSS) (CWE-79), Open Redirect (CWE-601). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-g4c2-ghfg-g5rh published, and has it been updated?

GHSA-g4c2-ghfg-g5rh was published on January 28, 2022 and was last updated on October 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-g4c2-ghfg-g5rh

MEDIUM

Cross-site Scripting and Open Redirect in Products.ATContentTypes

Also known asCVE-2022-23599PYSEC-2022-21

Published

Jan 28, 2022

Updated

Oct 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk50th percentile+0.42%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐍products-atcontenttypes

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Plone is vulnerable to reflected cross site scripting and open redirect when an attacker can get a compromised version of the image_view_fullscreen 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 image_view_fullscreen 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 'Enable caching' is not checked, you should normally not be vulnerable.
Click on the tab 'Caching operations'.
Under 'Legacy template mappings' locate the ruleset 'Content item view'.
From the last column ('Templates') remove 'image_view_fullscreen'.
Click on Save.

Reporter

This vulnerability was responsibly disclosed to the Plone Security Team by Gustav Hansen, F-Secure Consulting. Thank you!

For more information

If you have any questions or comments about this advisory, email us at [email protected] This is also the correct address to use when you want to report a possible vulnerability. See our security report policy.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`products-atcontenttypes`	all versions	3.0.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for products-atcontenttypes. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update products-atcontenttypes to 3.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g4c2-ghfg-g5rh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-g4c2-ghfg-g5rh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g4c2-ghfg-g5rh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Plone is vulnerable to reflected cross site scripting and open redirect when an attacker can get a compromised version of the image_view_fullscreen 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

O3 Security · Impact-Aware SCA

Is GHSA-g4c2-ghfg-g5rh in your dependencies?

O3 detects GHSA-g4c2-ghfg-g5rh across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works