Microblog Poster < 1.6.2 - Authenticated Blind SQL Injection
Strategic Overview
- Status
- Patched in 1.6.2
- Affected Plugin
- Microblog Poster – Auto Publish on Social Media
- Affected Version
< 1.6.2- CVSS
- 7.2High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2015-9449
At a glance
CVE-2015-9449 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Microblog Poster WordPress plugin, affecting versions < 1.6.2. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 1.6.2; sites on affected versions should update now. Disclosed July 2015, reported by Marcin Probola.
Vulnerability Overview
The microblog-poster plugin before 1.6.2 for WordPress has SQL Injection via the wp-admin/options-general.php?page=microblogposter.php account_id parameter.
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')
Reaching this weakness in Microblog Poster < 1.6.2 takes any authenticated account. 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 Microblog Poster the fix is 1.6.2: builds < 1.6.2 are affected, anything from 1.6.2 onward is not.
Remediation
Update to version 1.6.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Microblog Poster: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Microblog Poster 1.6.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Microblog Poster – Auto Publish on Social Media
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C