CVE-2007-2484

wp-Table <= 1.43 - Remote File Inclusion

2014-08-01 00:00
M.Hasran Addahroni

Strategic Overview

Status
Patched in 1.44
Affected Plugin
WP-Table
Affected Version
<= 1.43
CVSS
9.8Critical
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE-2007-2484
View all WP-Table vulnerabilities

At a glance

CVE-2007-2484 is a critical-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the WP-Table 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 August 2014, reported by M.Hasran Addahroni.

Vulnerability Overview

PHP remote file inclusion vulnerability in js/wptable-button.php in the wp-Table 1.43 and earlier plugin for WordPress, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the wpPATH parameter.

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-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Reaching this weakness in WP-Table <= 1.43 takes a caller who can reach the endpoint. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.

Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For WP-Table 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 WP-Table: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WP-Table 1.44 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

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