WP-Members Membership Plugin <= 3.5.4.2 - Authenticated (Subscriber+) Arbitrary Shortcode Execution via Profile Names
Strategic Overview
- Status
- Patched in 3.5.4.3
- Affected Plugin
- WP-Members Membership Plugin
- Affected Version
<= 3.5.4.2- CVSS
- 5.0Medium
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2025-9489
At a glance
CVE-2025-9489 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the WP-Members Membership Plugin WordPress plugin, affecting versions <= 3.5.4.2. It carries a CVSS score of 5.0 (reachable over the network). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.5.4.3; sites on affected versions should update now. Disclosed September 2025, reported by Kishan Vyas.
Vulnerability Overview
The The WP-Members Membership Plugin plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 3.5.4.2. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in WP-Members Membership Plugin <= 3.5.4.2 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 WP-Members Membership Plugin the fix is 3.5.4.3: builds <= 3.5.4.2 are affected, anything from 3.5.4.3 onward is not.
Remediation
Update to version 3.5.4.3, 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: WP-Members Membership Plugin 3.5.4.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in WP-Members Membership Plugin
- 8.8CVE-2019-15660: WP-Members <= 3.2.7 Cross-Site Request Forgery
CVE-2019-15660 - 7.2CVE-2024-1852: WP-Members Membership Plugin <= 3.4.9.2 Stored XSS
CVE-2024-1852 - 7.1WP-Members Membership Plugin <= 2.8.9 Reflected Cross-Site Scripting
- 6.5CVE-2026-2363: WP-Members Membership Plugin <= 3.5.5.1 SQL Injection
CVE-2026-2363 - 6.5CVE-2023-6733: WP-Members Membership Plugin <= 3.4.8 Info Exposure
CVE-2023-6733 - 6.4CVE-2025-57973: WP-Members <= 3.5.4.2 Stored Cross-Site Scripting
CVE-2025-57973 - 6.4CVE-2025-7495: WP-Members <= 3.5.4.1 Stored Cross-Site Scripting
CVE-2025-7495 - 6.4CVE-2025-50051: WP-Members <= 3.5.4 Stored Cross-Site Scripting
CVE-2025-50051
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C