CVE-2015-10139

WPLMS Learning Management System for WordPress, WordPress LMS <= 1.8.4.1 - Privilege Escalation

2015-02-08 00:00
Evex

Strategic Overview

Status
Patched in 1.9
Affected Version
<= 1.8.4.1
CVSS
8.8High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2015-10139
View all WPLMS Learning Management System for WordPress, WordPress LMS vulnerabilities

At a glance

CVE-2015-10139 is a high-severity Improper Privilege Management vulnerability in the WPLMS Learning Management System for WordPress, WordPress LMS WordPress theme, affecting versions <= 1.8.4.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.9; sites on affected versions should update now. Disclosed February 2015, reported by Evex.

Vulnerability Overview

The WPLMS theme for WordPress is vulnerable to Privilege Escalation in versions 1.5.2 to 1.8.4.1 via the 'wp_ajax_import_data' AJAX action. This makes it possible for authenticated attackers to change otherwise restricted settings and potentially create a new accessible admin account.

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-269: Improper Privilege Management

WPLMS Learning Management System for WordPress, WordPress LMS <= 1.8.4.1 carries this weakness at wp_ajax_import_data, and reaching it takes a caller who can reach the endpoint. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For WPLMS Learning Management System for WordPress, WordPress LMS the fix is 1.9: builds <= 1.8.4.1 are affected, anything from 1.9 onward is not.

Remediation

Update to version 1.9, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WPLMS Learning Management System for WordPress, WordPress LMS 1.9 closes this, and updating the theme is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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