CVE-2019-13344

WP Like Button <= 1.6.0 - Missing Authorization

2019-07-05 00:00
Benjamin Lim

Strategic Overview

Status
Patched in 1.6.1
Affected Plugin
WP Like Button
Affected Version
< 1.6.1
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2019-13344
View all WP Like Button vulnerabilities

At a glance

CVE-2019-13344 is a medium-severity Missing Authorization vulnerability in the WP Like Button WordPress plugin, affecting versions < 1.6.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.6.1; sites on affected versions should update now. Disclosed July 2019, reported by Benjamin Lim.

Vulnerability Overview

An authentication bypass vulnerability in the CRUDLab WP Like Button plugin through 1.6.0 for WordPress allows unauthenticated attackers to change settings. The contains() function in wp_like_button.php did not check if the current request is made by an authorized user, thus allowing any unauthenticated user to successfully update settings, as demonstrated by the wp-admin/admin.php?page=facebook-like-button each_page_url or code_snippet parameter.

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.

CWE-862: Missing Authorization

WP Like Button < 1.6.1 carries this weakness at contains(), and reaching it 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 Like Button the fix is 1.6.1: builds < 1.6.1 are affected, anything from 1.6.1 onward is not.

Remediation

Update to version 1.6.1, 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 Like Button 1.6.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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