Ultimate Member <= 1.3.64 - Local File Inclusion

2016-07-10 00:00
Burak Kelebek

Strategic Overview

Status
Patched in 1.3.65
Affected Plugin
Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
Affected Version
< 1.3.65
CVSS
9.1Critical
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE pending
View all Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin vulnerabilities

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 Ultimate Member WordPress plugin, affecting versions < 1.3.65. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.3.65; sites on affected versions should update now. Disclosed July 2016, reported by Burak Kelebek.

Vulnerability Overview

The Ultimate Member plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 1.3.64 via the 'page' parameter. 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 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')

Ultimate Member < 1.3.65 carries this weakness at page, 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 Ultimate Member the fix is 1.3.65: builds < 1.3.65 are affected, anything from 1.3.65 onward is not.

Remediation

Update to version 1.3.65, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Ultimate Member: 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: Ultimate Member 1.3.65 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/cc046b72-692a-4980-90ad-26c8fc2a131a

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C