CVE-2018-1000511

WP ULike < 3.2 - Missing Authorization

2018-05-14 00:00
Mallory Adams

Strategic Overview

Status
Patched in 3.2
Affected Plugin
WP ULike – Like Buttons, Voting & Engagement Analytics
Affected Version
< 3.2
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2018-1000511
View all WP ULike – Like Buttons, Voting & Engagement Analytics vulnerabilities

At a glance

CVE-2018-1000511 is a high-severity Missing Authorization vulnerability in the WP ULike WordPress plugin, affecting versions < 3.2. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 3.2; sites on affected versions should update now. Disclosed May 2018, reported by Mallory Adams.

Vulnerability Overview

The WP ULike plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the wp_ulike_logs_process function in versions before 3.2. This makes it possible for authenticated attackers with low-level privileges to delete any row of certain tables. This can also be exploited via Cross-Site Request Forgery due to a lack of nonce validation.

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 integrity.

CWE-862: Missing Authorization

Reaching this weakness in WP ULike < 3.2 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP ULike the fix is 3.2: builds < 3.2 are affected, anything from 3.2 onward is not.

Remediation

Update to version 3.2, 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: WP ULike 3.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2018-1000511https://www.wordfence.com/threat-intel/vulnerabilities/id/515a6a42-f353-47ae-9e74-4f9b2000bcb8https://nvd.nist.gov/vuln/detail/CVE-2018-1000511

Related records

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