Easy2Map <= 1.2.9 - Directory Traversal and Local File Inclusion
Strategic Overview
- Status
- Patched in 1.3.0
- Affected Plugin
- Easy2Map
- Affected Version
<= 1.2.9- CVSS
- 9.8Critical
- Weakness type
- CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
- CVE
CVE-2015-7669
At a glance
CVE-2015-7669 is a critical-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Easy2Map WordPress plugin, affecting versions <= 1.2.9. 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.3.0; sites on affected versions should update now. Disclosed October 2015, reported by Ibéria Medeiros.
Vulnerability Overview
Multiple directory traversal vulnerabilities in (1) includes/MapImportCSV2.php and (2) includes/MapImportCSV.php in the Easy2Map plugin before 1.3.0 for WordPress allow remote attackers to include and execute arbitrary files via the csvfile parameter related to "upload file functionality."
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 Easy2Map <= 1.2.9 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 Easy2Map the fix is 1.3.0: builds <= 1.2.9 are affected, anything from 1.3.0 onward is not.
Remediation
Update to version 1.3.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Easy2Map: 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: Easy2Map 1.3.0 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