Wp EMember < v10.9.4 - Unauthenticated SQL Injection
Strategic Overview
- Status
- Patched in v10.9.4
- Affected Plugin
- Wp EMember
- Affected Version
< v10.9.4- CVSS
- 7.5High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2026-54811
At a glance
CVE-2026-54811 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Wp EMember WordPress plugin, affecting versions < v10.9.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version v10.9.4; sites on affected versions should update now. Disclosed June 2026, reported by Tran Nguyen Bao Khanh.
Vulnerability Overview
The Wp EMember plugin for WordPress is vulnerable to SQL Injection in versions up to v10.9.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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. A successful exploit has high impact on confidentiality.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in Wp EMember < v10.9.4 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Wp EMember the fix is v10.9.4: builds < v10.9.4 are affected, anything from v10.9.4 onward is not.
Remediation
Update to version v10.9.4, 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: Wp EMember v10.9.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Wp EMember
- 9.1CVE-2024-5080: Wp EMember <= 10.6.5 Arbitrary File Upload
CVE-2024-5080 - 6.1CVE-2026-28073: Wp EMember <= 10.2.2 Reflected Cross-Site Scripting
CVE-2026-28073 - 6.1CVE-2024-5744: WP eMember <= 10.6.6 Reflected Cross-Site Scripting
CVE-2024-5744 - 6.1CVE-2024-5081: Wp EMember < 10.7.0 CSRF to Stored Cross-Site Scripting
CVE-2024-5081 - 6.1CVE-2024-5079: Wp EMember <= 10.6.6 Stored Cross-Site Scripting
CVE-2024-5079 - 6.1CVE-2024-5075: WP eMember <= 10.6.5 Reflected Cross-Site Scripting
CVE-2024-5075 - 6.1CVE-2024-5074: WP eMember <= 10.6.5 Reflected Cross-Site Scripting
CVE-2024-5074 - 6.1CVE-2024-5077: Wp EMember <= 10.6.5 Cross-Site Request Forgery
CVE-2024-5077
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C