How severe is CVE-2016-7139?

CVE-2016-7139 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2016-7139?

CVE-2016-7139 affects the following packages: plone (PyPI), plone (PyPI), plone (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2016-7139?

Update plone to 5.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-7139 is resolved across your whole dependency graph.

How do I detect CVE-2016-7139 in my PyPI dependencies?

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

How do I mitigate CVE-2016-7139 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-2016-7139 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2016-7139, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2016-7139?

CVE-2016-7139 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 76th 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-2016-7139?

CVE-2016-7139 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-2016-7139 published, and has it been updated?

CVE-2016-7139 was published on March 7, 2017 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-2016-7139 — plone

MEDIUM

CVE-2016-7139 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in plone. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for plone — see the affected versions and patch details below.

Plone Cross-site Scripting (XSS) vulnerability

Also known asGHSA-pp4c-2692-7f37PYSEC-2017-62

Published

Mar 7, 2017

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

2 / 3

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs76th percentile — riskier than 76% 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

3 pkgs affected

🐍plone🐍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

Cross-site scripting (XSS) vulnerability in an unspecified page template in Plone CMS 5.x through 5.0.6, 4.x through 4.3.11, and 3.3.x through 3.3.6 allows remote attackers to inject arbitrary web script or HTML via unknown vectors.

Affected Packages

3 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`plone`	≥ 5.0&&< 5.0.6	5.0.6`pip install --upgrade 'plone==5.0.6'`
🐍PyPI	`plone`	≥ 4.0a1&&< 4.3.12	4.3.12`pip install --upgrade 'plone==4.3.12'`
🐍PyPI	`plone`	≥ 3.3	No fix

Affected Products

1 product · 56 configurations

Application

ploneplone

52 versions

3.33.3.13.3.23.3.33.3.43.3.53.3.64.04.0.14.0.24.0.34.0.4

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Cross-site scripting (XSS) vulnerability in an unspecified page template…

packetstormsecurity.comNVDOct 2018

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update plone to 5.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-7139 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

O3 Security · Impact-Aware SCA

Is CVE-2016-7139 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Mar 7, 2017

First exploit

Oct 9, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2016-7139

GHSA-pp4c-2692-7f37

PYSEC-2017-62

References

Advisoryseclists.org Advisoryplone.org · non persistent xss in plone Advisorynvd.nist.gov · CVE 2016 7139 Fixopenwall.com Fixopenwall.com Websecurityfocus.com · threaded Websecurityfocus.com Webgithub.com · PYSEC 2017 62.yaml Webweb.archive.org Webweb.archive.org · threaded Packagegithub.com · Plone Evidencepacketstormsecurity.com · Plone CMS 4.3.11 5.0.6 XSS Traversal Open Redirection

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; 4 of 4 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-44267CVE-2026-96632CVE-2026-9086CVE-2026-118246Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026