WP Email Users <= 1.4.4 - SQL Injection
Strategic Overview
- Status
- Patched in 1.4.5
- Affected Plugin
- WP Email Users
- Affected Version
<= 1.4.4- CVSS
- 8.8High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE pending
At a glance
This record tracks a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP Email Users WordPress plugin, affecting versions <= 1.4.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.4.5; sites on affected versions should update now. Disclosed January 2017, reported by Lenon Leite.
Vulnerability Overview
The WP Email Users plugin for WordPress is vulnerable to SQL Injection via the ‘filetitle’ parameter in versions up to, and including, 1.4.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 authenticated attackers with subscriber-level permissions 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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
WP Email Users <= 1.4.4 carries this weakness at filetitle, and reaching it takes a caller who can reach the endpoint. 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 Email Users the fix is 1.4.5: builds <= 1.4.4 are affected, anything from 1.4.5 onward is not.
Remediation
Update to version 1.4.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Email Users: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Email Users 1.4.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C