ChurcHope <= 2.1 - Local File Inclusion
Strategic Overview
- Status
- Patched in 2.2
- Affected Theme
- ChurcHope
- Affected Version
<= 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 pending
At a glance
This record tracks a critical-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the ChurcHope WordPress theme, affecting versions <= 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 2.2; sites on affected versions should update now. Disclosed December 2014.
Vulnerability Overview
The ChurcHope theme for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2.1 via the 'file' parameter in the 'downloadlink.php' file. This allows unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
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')
ChurcHope <= 2.1 carries this weakness at file, and reaching it 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 ChurcHope 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 ChurcHope: 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: ChurcHope 2.2 closes this, and updating the theme is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C