Paid Memberships Pro <= 2.0.5 - Open Redirect

2019-06-01 00:00
Anonymous

Strategic Overview

Status
Patched in 2.0.6
Affected Plugin
Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions
Affected Version
<= 2.0.5
CVSS
7.2High
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE pending
View all Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions vulnerabilities

At a glance

This record tracks a high-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Paid Memberships Pro WordPress plugin, affecting versions <= 2.0.5. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.6; sites on affected versions should update now. Disclosed June 2019.

Vulnerability Overview

The Paid Memberships Pro plugin for WordPress is vulnerable to an open redirect vulnerability in versions up to, and including, 2.0.5. This is due to missing redirect location verification on the pmpro_redirect_to_logged_in() function. This makes it possible for authenticated attackers to redirect traffic to a different website, where they could potentially perform other attacks; such as phishing.

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

Paid Memberships Pro <= 2.0.5 carries this weakness at pmpro_redirect_to_logged_in(), and reaching it 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 Paid Memberships Pro the fix is 2.0.6: builds <= 2.0.5 are affected, anything from 2.0.6 onward is not.

Remediation

Update to version 2.0.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Paid Memberships Pro: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Paid Memberships Pro 2.0.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/78bb5e18-5535-4cee-a38b-e38802059ef7

Related records

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