MelaPress Login Security <= 1.3.0 - Authenticated (Admin+) Remote File Inclusion
Strategic Overview
- Status
- Patched in 1.3.1
- Affected Plugin
- Melapress Login Security
- Affected Version
<= 1.3.0- CVSS
- 6.6Medium
- Weakness type
- CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
- CVE
CVE-2024-35650
At a glance
CVE-2024-35650 is a medium-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Melapress Login Security WordPress plugin, affecting versions <= 1.3.0. It carries a CVSS score of 6.6 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.3.1; sites on affected versions should update now. Disclosed June 2024, reported by YC_Infosec.
Vulnerability Overview
The MelaPress Login Security plugin for WordPress is vulnerable to Remote File Inclusion in all versions up to, and including, 1.3.0 via the 'tab' parameter. This makes it possible for authenticated attackers, with Administrator-level access and above, to include and execute arbitrary files hosted on remote servers, 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. This requires the site to have the allow_url_include setting to be enabled.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, 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')
Melapress Login Security <= 1.3.0 carries this weakness at tab, and reaching it takes an account at Admin level or above. 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 Melapress Login Security the fix is 1.3.1: builds <= 1.3.0 are affected, anything from 1.3.1 onward is not.
Remediation
Update to version 1.3.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: 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: Melapress Login Security 1.3.1 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