WordPress component - Path Traversal (CVE-2017-1000170)
CVE-2017-1000170
jqueryFileTree 2.1.5 and older Directory Traversal
CVE-2017-1000170
CVE-2017-1000170
jqueryFileTree 2.1.5 and older Directory Traversal
CVE-2017-1000170
Machine-generated threat intelligence
AI Updated just now
AI enriched just now (2026-09-18 20:10 UTC)
jqueryFileTree 2.1.5 and older Directory Traversal
Severity is HIGH (CVSS 7.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability is assessed as Medium based on published exploit references.
Primary risk drivers: published exploit references
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
AI risk score 78/100 (High, Medium) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.
Patch promptly The consequence is significant even where an attacker needs a foothold first.
Update WordPress component to the latest available version.
Where the vendor has not published a fix yet, disable the plugin until they do.
No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.
Scan your site to see whether it runs WordPress component, and at which version.
Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.
You are affected if your site runs WordPress component.
Update WordPress component to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do.
This is a Path Traversal flaw. An attacker who exploits it can read files outside the intended directory, including wp-config.php.