How severe is GHSA-8w54-22w9-3g8f?

GHSA-8w54-22w9-3g8f 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-8w54-22w9-3g8f?

GHSA-8w54-22w9-3g8f affects the following packages: products-cmfplone (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-8w54-22w9-3g8f?

Update products-cmfplone to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8w54-22w9-3g8f is resolved across your whole dependency graph.

How do I detect GHSA-8w54-22w9-3g8f in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for products-cmfplone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8w54-22w9-3g8f if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is GHSA-8w54-22w9-3g8f actively exploited in the wild?

No public exploit code has been indexed for GHSA-8w54-22w9-3g8f 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.

When was GHSA-8w54-22w9-3g8f published, and has it been updated?

GHSA-8w54-22w9-3g8f was published on January 28, 2022 and was last updated on December 5, 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

Not in CISA KEV

MEDIUM severity

Cross-site Scripting and Open Redirect in Products.CMFPloneGHSA-8w54-22w9-3g8f

MEDIUM

GHSA-8w54-22w9-3g8f is a medium-severity (CVSS 4.3) vulnerability in products-cmfplone. A fix is available for products-cmfplone — see the affected versions and patch details below.

Published

Jan 28, 2022

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 5, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍products-cmfplone

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

No patch is available for the Products.CMFPlone 4 series. Versions 5.0 and higher are not affected, but two other packages used by these versions are affected.

plone.app.contenttypes has the same problem in all versions, see advisory. In Plone 5.0-5.2, the default Products.ATContentTypes version has the same problem. See advisory. Plone 5.2.7 and 6.0.0a3 will be released today and will include these fixes.

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-cmfplone`	all versions	5.0.0`pip install --upgrade 'products-cmfplone==5.0.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for products-cmfplone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update products-cmfplone to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8w54-22w9-3g8f is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

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 No patch is available for the Products.CMFPlone 4 series. Versions 5.0 and higher are not affected, but two other packages used by these versions are affected. `plone.app.contenttypes`

O3 Security · Impact-Aware SCA

Is GHSA-8w54-22w9-3g8f in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works