Strategic Overview
- Status
- Patched in 3.1.9.1
- Affected Plugin
- WPML Multilingual CMS
- Affected Version
<= 3.1.9- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2015-2314
At a glance
CVE-2015-2314 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WPML Multilingual CMS WordPress plugin, affecting versions <= 3.1.9. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.1.9.1; sites on affected versions should update now. Disclosed March 2015, reported by Jouko Pynnöne.
Vulnerability Overview
SQL injection vulnerability in the WPML plugin before 3.1.9.1 for WordPress allows remote attackers to execute arbitrary SQL commands via the lang parameter in the HTTP Referer header in a wp-link-ajax action to comments/feed.
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, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in WPML Multilingual CMS <= 3.1.9 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 WPML Multilingual CMS the fix is 3.1.9.1: builds <= 3.1.9 are affected, anything from 3.1.9.1 onward is not.
Remediation
Update to version 3.1.9.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WPML Multilingual CMS: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPML Multilingual CMS 3.1.9.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WPML Multilingual CMS
- 9.9CVE-2024-6386: WPML Multilingual CMS <= 4.6.12 Remote Code Execution
CVE-2024-6386 - 8.8CVE-2020-10568: WPML < 4.3.7 Cross-Site Request Forgery Bypass
CVE-2020-10568 - 7.5CVE-2015-2791: WPML <= 3.1.9 Arbitrary Deletion of Content
CVE-2015-2791 - 7.2CVE-2018-18069: WPML <= 3.6.3 Stored Cross-Site Scripting
CVE-2018-18069 - 6.4CVE-2025-3488: WPML Multilingual CMS 3.6.0 - 4.7.3 Stored XSS
CVE-2025-3488 - 6.1WPML <= 4.6.0 Reflected Cross-Site Scripting via wp_lang
- 6.1CVE-2015-9416: WPML 2.9.3-3.2.6 XSS in Accept-Language Header
CVE-2015-9416 - 5.4WPML <= 4.5.10 Unprotected AJAX Actions
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C