CVE-2017-1000482 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in products-cmfplone. A fix is available for products-cmfplone — see the affected versions and patch details below.
Products.CMFPlone XSS in profile home_page property
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
CVE-2017-1000482 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,636 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
A member of the Plone 2.5-5.1rc1 site could set javascript in the home_page property of his profile, and have this executed when a visitor click the home page link on the author page.
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.5a1&&< 4.3.16 | 4.3.16pip install --upgrade 'plone==4.3.16' |
| 🐍PyPI | plone | ≥ 5.0a1&&< 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 CVE-2017-1000482 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 CVE-2017-1000482 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2017-1000482. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2017-1000482 in your dependencies?
O3 Security finds CVE-2017-1000482 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.