Fusion <= 2.1 - Arbitrary File Download
Strategic Overview
- Status
- Patched in 2.2
- Affected Theme
- Fusion
- Affected Version
<= 2.1- CVSS
- 7.5High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE pending
At a glance
This record tracks a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Fusion WordPress theme, affecting versions <= 2.1. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.2; sites on affected versions should update now. Disclosed December 2013.
Vulnerability Overview
The Fusion Theme for WordPress is vulnerable to Arbitrary File Download in versions up to, and including, 2.1. This is due to the '_mysite_download_skin' parameter in the 'dl-skin.php' file. This makes it possible for unauthenticated attackers to download any file within the server of the vulnerable service.
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.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Fusion <= 2.1 carries this weakness at _mysite_download_skin, 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 Fusion the fix is 2.2: builds <= 2.1 are affected, anything from 2.2 onward is not.
Remediation
Update to version 2.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Fusion: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Fusion 2.2 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C