CVE-2025-47691

Ultimate Member <= 2.10.3 - Authenticated (Administrator+) Arbitrary Function Call

Strategic Overview

At a glance

CVE-2025-47691 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Ultimate Member WordPress plugin, affecting versions <= 2.10.3. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 2.10.4; sites on affected versions should update now. Disclosed May 2025, reported by Trương Hữu Phúc (truonghuuphuc).

Vulnerability Overview

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to Arbitrary Function Calls in all versions up to, and including, 2.10.3. This is due to the plugin not properly restricting functions that can be called. This makes it possible for authenticated attackers, with Administrator-level access and above, to execute arbitrary functions making remote code execution possible.

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, availability — full site compromise territory.

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

Reaching this weakness in Ultimate Member <= 2.10.3 takes an account at Administrator 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 Ultimate Member the fix is 2.10.4: builds <= 2.10.3 are affected, anything from 2.10.4 onward is not.

Remediation

Update to version 2.10.4, or a newer patched version

How does WordSec protect against this?

An attacker needs Administrator 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: Ultimate Member 2.10.4 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