Ultimate Member <= 2.1.6 - Open Redirect

2020-07-23 00:00
tonyko

Strategic Overview

Status
Patched in 2.1.7
Affected Plugin
Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
Affected Version
< 2.1.7
CVSS
6.1Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE pending
View all Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin vulnerabilities

At a glance

This record tracks a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Ultimate Member WordPress plugin, affecting versions < 2.1.7. 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.1.7; sites on affected versions should update now. Disclosed July 2020, reported by tonyko.

Vulnerability Overview

The Ultimate Member plugin for WordPress is vulnerable to open redirects in versions up to, and including, 2.1.6 This is due to insufficient redirect location validation which makes it possible for unauthenticated attackers to trick victims into accessing malicious sites granted they can trick the victim into performing an action such as clicking on a link.

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-601: URL Redirection to Untrusted Site ('Open Redirect')

Reaching this weakness in Ultimate Member < 2.1.7 takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For Ultimate Member the fix is 2.1.7: builds < 2.1.7 are affected, anything from 2.1.7 onward is not.

Remediation

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/db3b206d-16c5-48fb-800d-d017a0c76630

Related records

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