How severe is CVE-2016-6600?

No CVSS score has been assigned to CVE-2016-6600 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2016-6600?

Affected package information for CVE-2016-6600 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2016-6600?

No fixed release is recorded for CVE-2016-6600 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2016-6600 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2016-6600 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2016-6600 actively exploited in the wild?

Yes. There are 7 known exploit references for CVE-2016-6600, including 1 documented proof-of-concept exploit on Exploit-DB and 6 in-the-wild exploitations 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-6600?

CVE-2016-6600 has an EPSS (Exploit Prediction Scoring System) score of 90.8%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2016-6600?

CVE-2016-6600 is classified as Path Traversal (CWE-22). 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-6600 published, and has it been updated?

CVE-2016-6600 was published on January 23, 2017 and was last updated on August 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2016-6600 — Pedrib

CVE-2016-6600 is a Path Traversal vulnerability. 7 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Directory traversal vulnerability in the file upload functionality in ZOHO WebNMS Framework 5.2 and 5.2 SP1 allows remote attackers to upload and execute arbitrary JSP files via a ..…

Published

Jan 23, 2017

Updated

Aug 6, 2024

Affected

1 product

Patched

See advisory

Exploits

7 known

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

EPSS Exploitation Probability

via FIRST.org ↗

90.8%probability of exploitation in next 30 days

Very High Risk+0.24%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

Description

Directory traversal vulnerability in the file upload functionality in ZOHO WebNMS Framework 5.2 and 5.2 SP1 allows remote attackers to upload and execute arbitrary JSP files via a .. (dot dot) in the fileName parameter to servlets/FileUploadServlet.

Affected Products

1 product · 2 configurations

Application

webnms frameworkzohocorp

1 version

5.2

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.

EDB-40229webappsjsp

WebNMS Framework Server 5.2/5.2 SP1 - Multiple Vulnerabilities

by Pedro Ribeiro · Aug 10, 2016

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2016-6600 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-6600 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works