CVE-2017-1000226

Stop User Enumeration plugin <1.3.9 - User Enumeration

2017-05-16 00:00
Mallory Adams

Strategic Overview

Status
Patched in 1.3.9
Affected Plugin
Stop User Enumeration
Affected Version
< 1.3.9
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2017-1000226
View all Stop User Enumeration vulnerabilities

At a glance

CVE-2017-1000226 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Stop User Enumeration WordPress plugin, affecting versions < 1.3.9. 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.3.9; sites on affected versions should update now. Disclosed May 2017, reported by Mallory Adams.

Vulnerability Overview

The Stop User Enumeration plugin for WordPress is vulnerable to User Enumeration in versions up to, and including, 1.3.8. This is due to a flaw that was found in the REST API. This makes it possible for unauthenticated attackers to perform a POST request in the REST API allows simulating different request types. As such, attackers can perform a POST request with the “users” string in the body of the request, and tell the REST API to act like it’s received a GET request.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Stop User Enumeration < 1.3.9 carries this weakness at users, and reaching it takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Stop User Enumeration the fix is 1.3.9: builds < 1.3.9 are affected, anything from 1.3.9 onward is not.

Remediation

Update to version 1.3.9, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Stop User Enumeration 1.3.9 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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