Strategic Overview
- Status
- Patched in 2.3.5
- Affected Plugin
- SlideDeck 2 Lite Responsive Content Slider
- Affected Version
<= 2.3.3- CVSS
- 9.8Critical
- Weakness type
- CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
- CVE
CVE-2013-7483
At a glance
CVE-2013-7483 is a critical-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the SlideDeck 2 Lite Responsive Content Slider WordPress plugin, affecting versions <= 2.3.3. 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 2.3.5; sites on affected versions should update now. Disclosed August 2014.
Vulnerability Overview
The SlideDeck 2 plugin for WordPress is vulnerable to Local/Remote File Inclusion in versions up to, and including, 2.3.3. This allows unauthenticated attackers to include local/remote files on the server, resulting in 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-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Reaching this weakness in SlideDeck 2 Lite Responsive Content Slider <= 2.3.3 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 SlideDeck 2 Lite Responsive Content Slider the fix is 2.3.5: builds <= 2.3.3 are affected, anything from 2.3.5 onward is not.
Remediation
Update to version 2.3.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to SlideDeck 2 Lite Responsive Content Slider: 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: SlideDeck 2 Lite Responsive Content Slider 2.3.5 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