Strategic Overview
- Status
- Patched in 1.4.4
- Affected Plugin
- WassUp Real Time Analytics
- Affected Version
1.4 – 1.4.3- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2008-0520
At a glance
CVE-2008-0520 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WassUp Real Time Analytics WordPress plugin, affecting versions 1.4 – 1.4.3. 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 1.4.4; sites on affected versions should update now. Disclosed January 2008, reported by enter_the_dragon.
Vulnerability Overview
Multiple SQL injection vulnerabilities in main.php in the WassUp plugin 1.4 through 1.4.3 for WordPress allow remote attackers to execute arbitrary SQL commands via the (1) from_date or (2) to_date parameter to spy.php.
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 WassUp Real Time Analytics 1.4 – 1.4.3 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 WassUp Real Time Analytics the fix is 1.4.4: builds 1.4 – 1.4.3 are affected, anything from 1.4.4 onward is not.
Remediation
Update to version 1.4.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WassUp Real Time Analytics: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WassUp Real Time Analytics 1.4.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WassUp Real Time Analytics
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C