CVE-2019-14946

Ultimate Member <= 2.0.51 - Cross-Site Request Forgery and Stored Cross-Site Scripting

2019-06-24 00:00
m0ns7er

Strategic Overview

Status
Patched in 2.0.52
Affected Version
<= 2.0.51
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2019-14946
View all Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin vulnerabilities

At a glance

CVE-2019-14946 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Ultimate Member WordPress plugin, affecting versions <= 2.0.51. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.52; sites on affected versions should update now. Disclosed June 2019, reported by m0ns7er.

Vulnerability Overview

The ultimate-member plugin before 2.0.52 for WordPress has XSS related to UM Roles create and edit operations.

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.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Ultimate Member <= 2.0.51 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Ultimate Member the fix is 2.0.52: builds <= 2.0.51 are affected, anything from 2.0.52 onward is not.

Remediation

Update to version 2.0.52, 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. None of that substitutes for the fix: Ultimate Member 2.0.52 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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