Express Payments Module <= 1.1.8 - Unauthenticated SQL Injection via type_id
Strategic Overview
- Status
- Patched in 1.1.9
- Affected Plugin
- ExpressPay Payment Module
- Affected Version
<= 1.1.8- CVSS
- 7.5High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2024-52474
At a glance
CVE-2024-52474 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the ExpressPay Payment Module WordPress plugin, affecting versions <= 1.1.8. 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 1.1.9; sites on affected versions should update now. Disclosed November 2024, reported by LVT-tholv2k.
Vulnerability Overview
The Express Payments Module plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 1.1.8 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 ExpressPay Payment Module <= 1.1.8 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 ExpressPay Payment Module the fix is 1.1.9: builds <= 1.1.8 are affected, anything from 1.1.9 onward is not.
Remediation
Update to version 1.1.9, 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: ExpressPay Payment Module 1.1.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C