How severe is CVE-2017-1000482?

CVE-2017-1000482 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-1000482?

CVE-2017-1000482 affects the following packages: products-cmfplone (PyPI), products-cmfplone (PyPI), products-cmfplone (PyPI), plone (PyPI), plone (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2017-1000482?

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.

How do I detect CVE-2017-1000482 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 CVE-2017-1000482 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2017-1000482 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-1000482 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 CVE-2017-1000482?

CVE-2017-1000482 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th 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 CVE-2017-1000482?

CVE-2017-1000482 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type 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 CVE-2017-1000482 published, and has it been updated?

CVE-2017-1000482 was published on January 3, 2018 and was last updated on October 24, 2026. 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

CVE-2017-1000482 — products-cmfplone

MEDIUMFix: plone/Products.CMFPlone#2233

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

Also known asGHSA-859j-668v-mrr6PYSEC-2018-71PYSEC-2026-2962

Published

Jan 3, 2018

Updated

Oct 24, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

🐍products-cmfplone🐍products-cmfplone🐍products-cmfplone🐍plone🐍plone

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

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

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`products-cmfplone`	all versions	4.3.17`pip install --upgrade 'products-cmfplone==4.3.17'`
🐍PyPI	`products-cmfplone`	≥ 5.0.0&&< 5.0.10	5.0.10`pip install --upgrade 'products-cmfplone==5.0.10'`
🐍PyPI	`products-cmfplone`	≥ 5.1a1&&< 5.1.0	5.1.0`pip install --upgrade 'products-cmfplone==5.1.0'`
🐍PyPI	`plone`	≥ 2.5a1&&< 4.3.16	4.3.16`pip install --upgrade 'plone==4.3.16'`
🐍PyPI	`plone`	≥ 5.0a1&&< 5.1.0	5.1.0`pip install --upgrade 'plone==5.1.0'`

Affected Products

1 product · 7 configurations

Application

ploneplone

≤ 5.0.9

1 version

5.1

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 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
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2017-1000482 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jan 3, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2017-1000482

GHSA-859j-668v-mrr6

PYSEC-2018-71

PYSEC-2026-2962

References

Advisoryplone.org · xss using the home page member property Advisorynvd.nist.gov · CVE 2017 1000482 Webgithub.com Webgithub.com Webgithub.com Webgithub.com Webgithub.com Webgithub.com · 05a943ecbcdda56bacc93b55c9e2e908d8a7dfab Webgithub.com · 0e50e1e67ea3b6d3187f78cb1a1628081f654d3b Webgithub.com · 236b62b756ff46a92783b3897e717dfb15eb07d8 Webgithub.com · 7db5b2c8fb684055987b8c4fdedc29289bd26373 Webgithub.com · PYSEC 2018 71.yaml Packagegithub.com · Products.CMFPlone

Related vulnerabilities

Also affects plone

This CVE is medium severity, in line with the other 4 CVEs affecting plone.

CVE-2021-29002CVE-2011-1340CVE-2008-1396CVE-2006-1711

Same weakness: CWE-79

This CVE is medium severity; 2 of 4 other CVEs with CWE-79 are rated as high or higher (top: moderate).

CVE-2026-126075CVE-2026-126063CVE-2026-110802CVE-2026-123364Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026