CVE-2026-92798

User Registration & Membership <= 5.2.8 - Authenticated (Subscriber+) Arbitrary Shortcode Execution via Referer Header via 'referrer_url' Smart Tag

2026-10-16 14:42
Passakorn Yookindee

At a glance

CVE-2026-92798 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the User Registration & Membership WordPress plugin, affecting versions <= 5.2.8. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.3.0; sites on affected versions should update now. Disclosed October 2026, reported by Passakorn Yookindee.

Vulnerability Overview

The User Registration & Membership plugin for WordPress is vulnerable to Arbitrary Shortcode Execution in versions up to, and including, 5.2.8 This is due to insufficient input sanitization in the 'referrer_url' branch of UR_Smart_Tags::process(), where the attacker-controlled HTTP_REFERER header is only passed through sanitize_text_field() — which does not strip WordPress shortcode delimiters — before being substituted into a Content Restriction message that is subsequently executed via apply_shortcodes()/do_shortcode(). This makes it possible for unauthenticated attackers to execute arbitrary registered shortcodes on any restricted page whose message uses the supported {{referrer_url}} smart tag.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity.

CWE-94: Improper Control of Generation of Code ('Code Injection')

User Registration & Membership <= 5.2.8 carries this weakness at referrer_url, and reaching it takes an account at Subscriber level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For User Registration & Membership the fix is 5.3.0: builds <= 5.2.8 are affected, anything from 5.3.0 onward is not.

Remediation

Update to version 5.3.0, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: User Registration & Membership 5.3.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

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