CVE-2007-2426

MySliderGallery <= 1.2.1 - Remote File Inclusion

2007-04-29 00:00
GolD_M

Strategic Overview

Status
Patched in 1.4b5
Affected Plugin
MySliderGallery
Affected Version
<= 1.2.1
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-2426
View all MySliderGallery vulnerabilities

At a glance

CVE-2007-2426 is a critical-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the MySliderGallery WordPress plugin, affecting versions <= 1.2.1. 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.4b5; sites on affected versions should update now. Disclosed April 2007, reported by GolD_M.

Vulnerability Overview

PHP remote file inclusion vulnerability in myfunctions/mygallerybrowser.php in the myGallery 1.2.1 and earlier plugin for WordPress allows remote attackers to execute arbitrary PHP code via a URL in the myPath parameter. Note that this uses the same slug as a newer plugin that is not vulnerable.

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 MySliderGallery <= 1.2.1 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 MySliderGallery the fix is 1.4b5: builds <= 1.2.1 are affected, anything from 1.4b5 onward is not.

Remediation

Update to version 1.4b5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to MySliderGallery: 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: MySliderGallery 1.4b5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

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