How severe is CVE-2017-1000170?

CVE-2017-1000170 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-1000170?

CVE-2017-1000170 affects the following packages: jqueryfiletree (npm). Ecosystems affected: npm.

How do I fix CVE-2017-1000170?

No patched version of jqueryfiletree has shipped for CVE-2017-1000170 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2017-1000170 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jqueryfiletree. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

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 does O3 Security protect against CVE-2017-1000170?

O3 pinpoints whether CVE-2017-1000170 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Yes. There are 5 known exploit references for CVE-2017-1000170, including 1 documented proof-of-concept exploit on Exploit-DB and 3 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-2017-1000170?

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

CVE-2017-1000170 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.

Is there exploit tooling available for CVE-2017-1000170?

A Nuclei detection template exists for CVE-2017-1000170, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2017-1000170 published, and has it been updated?

CVE-2017-1000170 was published on November 17, 2017 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

CVE-2017-1000170

HIGH

jqueryFileTree vulnerable to Directory Traversal

Also known asGHSA-p739-9479-5wr2

Published

Nov 17, 2017

Updated

Jul 8, 2026

Affected

1 pkg

Patched

None yet

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

59.1%probability of exploitation in next 30 days

High Risk99th percentile+1.45%

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.

Blast Radius

1 pkg affected

📦jqueryfiletree

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

jqueryFileTree 2.1.5 and older Directory Traversal

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`jqueryfiletree`	all versions	No fix

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-49693webappsphp

WordPress Plugin Delightful Downloads Jquery File Tree 1.6.6 - Path Traversal

by Nicholas Ferreira · Mar 22, 2021

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jqueryfiletree. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of jqueryfiletree has shipped for CVE-2017-1000170 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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 pinpoints whether CVE-2017-1000170 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2017-1000170. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

jqueryFileTree 2.1.5 and older Directory Traversal

O3 Security · Impact-Aware SCA

Is CVE-2017-1000170 in your dependencies?

O3 detects CVE-2017-1000170 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVE-2017-1000170

EPSS Exploitation Probability

Blast Radius

Description

Affected Packages

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2017-1000170 in your dependencies?