CVE-2007-2482

wordTube <= 1.43 - Directory Traversal and File Inclusion

2007-05-01 00:00
M.Hasran Addahroni

Strategic Overview

Status
Patched in 1.44
Affected Plugin
wordTube
Affected Version
<= 1.43
CVSS
9.8Critical
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2007-2482
View all wordTube vulnerabilities

At a glance

CVE-2007-2482 is a critical-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the wordTube WordPress plugin, affecting versions <= 1.43. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.44; sites on affected versions should update now. Disclosed May 2007, reported by M.Hasran Addahroni.

Vulnerability Overview

The wordTube plugin for WordPress is vulnerable to Directory Traversal in versions up to, and including, 1.43 via the 'wpPATH' parameter found in the wordtube-button.php file. This makes it possible for attackers to read the contents of arbitrary files on the server, which can contain sensitive information. This can also be used to include remote and local files to achieve remote code execution.

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, integrity, availability — full site compromise territory.

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

wordTube <= 1.43 carries this weakness at wpPATH, and reaching it 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 wordTube the fix is 1.44: builds <= 1.43 are affected, anything from 1.44 onward is not.

Remediation

Update to version 1.44, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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