CVE-2026-80072

User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder < 5.2.8 - Unauthenticated Open Redirect

2026-09-11 00:00
Sai Praneeth Koti

At a glance

CVE-2026-80072 is a high-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the User Registration & Membership WordPress plugin, affecting versions < 5.2.8. 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 5.2.8; sites on affected versions should update now. Disclosed September 2026, reported by Sai Praneeth Koti.

Vulnerability Overview

The User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder plugin for WordPress is vulnerable to Open Redirect in all versions up to 5.2.8 (exclusive). This is due to insufficient validation on the redirect url. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action.

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')

Reaching this weakness in User Registration & Membership < 5.2.8 takes no account at all. 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 User Registration & Membership the fix is 5.2.8: builds < 5.2.8 are affected, anything from 5.2.8 onward is not.

Remediation

Update to version 5.2.8, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: User Registration & Membership 5.2.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

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