CVE-2014-10390

WP Support Plus Responsive Ticket System <= 4.1 - Directory Traversal

2014-11-15 00:00
Fikri Fadzil

Strategic Overview

Status
Patched in 4.2
Affected Plugin
WP Support Plus Responsive Ticket System
Affected Version
< 4.2
CVSS
7.5High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2014-10390
View all WP Support Plus Responsive Ticket System vulnerabilities

At a glance

CVE-2014-10390 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP Support Plus Responsive Ticket System WordPress plugin, affecting versions < 4.2. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.2; sites on affected versions should update now. Disclosed November 2014, reported by Fikri Fadzil.

Vulnerability Overview

The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has directory traversal.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in WP Support Plus Responsive Ticket System < 4.2 takes a caller who can reach the endpoint. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For WP Support Plus Responsive Ticket System the fix is 4.2: builds < 4.2 are affected, anything from 4.2 onward is not.

Remediation

Update to version 4.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Support Plus Responsive Ticket System: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Support Plus Responsive Ticket System 4.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2014-10390https://www.wordfence.com/threat-intel/vulnerabilities/id/99433521-721b-41c3-8736-fd2943901b4fhttps://nvd.nist.gov/vuln/detail/CVE-2014-10390

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C