GHSA-8g72-gq68-6gqh is a medium-severity (CVSS 6.1) Open Redirect vulnerability in products-cmfplone. A fix is available for products-cmfplone — see the affected versions and patch details below.
Products.CMFPlone Open Redirect Vulnerability
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-8g72-gq68-6gqh plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
products-cmfplone🐍products-cmfplone🐍products-cmfplone🐍plone🐍ploneReal-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
When you visit a page where you need to login, Plone 2.5-5.1rc1 sends you to the login form with a 'came_from' parameter set to the previous url. After you login, you get redirected to the page you tried to view before. An attacker might try to abuse this by letting you click on a specially crafted link. You would login, and get redirected to the site of the attacker, letting you think that you are still on the original Plone site. Or some javascript of the attacker could be executed. Most of these types of attacks are already blocked by Plone, using the isURLInPortal check to make sure we only redirect to a page on the same Plone site. But a few more ways of tricking Plone into accepting a malicious link were discovered, and fixed with this hotfix.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | products-cmfplone | all versions | 4.3.17pip install --upgrade 'products-cmfplone==4.3.17' |
| 🐍PyPI | products-cmfplone | ≥ 5.0.0&&< 5.0.10 | 5.0.10pip install --upgrade 'products-cmfplone==5.0.10' |
| 🐍PyPI | products-cmfplone | ≥ 5.1a1&&< 5.1.0 | 5.1.0pip install --upgrade 'products-cmfplone==5.1.0' |
| 🐍PyPI | plone | ≥ 2.5&&< 4.3.16 | 4.3.16pip install --upgrade 'plone==4.3.16' |
| 🐍PyPI | plone | ≥ 5&&< 5.1.0 | 5.1.0pip install --upgrade 'plone==5.1.0' |
Detection & mitigation playbook
Open-source dependencyDetect
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 4.3.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8g72-gq68-6gqh 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8g72-gq68-6gqh can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8g72-gq68-6gqh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8g72-gq68-6gqh in your dependencies?
O3 Security finds GHSA-8g72-gq68-6gqh across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.