WP Statistics <= 13.2.5 - Authenticated (Subscriber+) SQL Injection
Strategic Overview
- Status
- Patched in 13.2.6
- Affected Version
<= 13.2.5- 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 Statistics WordPress plugin, affecting versions <= 13.2.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 13.2.6; sites on affected versions should update now. Disclosed September 2022.
Vulnerability Overview
The WP Statistics plugin for WordPress is vulnerable to time-based blind SQL Injection via the ‘agent’ parameter in versions up to, and including, 13.2.5 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 access or higher, 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 Statistics <= 13.2.5 carries this weakness at agent, and reaching it takes an account at Subscriber level or above. 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 Statistics the fix is 13.2.6: builds <= 13.2.5 are affected, anything from 13.2.6 onward is not.
Remediation
Update to version 13.2.6, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Statistics 13.2.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Statistics – Simple, privacy-friendly Google Analytics alternative
- 9.8CVE-2019-13275: WP Statistics <= 12.6.6.1 Blind SQL Injection
CVE-2019-13275 - 8.8CVE-2022-38074: WP Statistics <= 13.2.10 SQL Injection
CVE-2022-38074 - 8.8CVE-2017-18515: WP Statistics <= 12.0.7 SQL Injection
CVE-2017-18515 - 8.7WP Statistics < 9.4.1 Blind SQL Injection
- 7.5CVE-2021-24340: WP Statistics <= 13.0.7 SQL Injection
CVE-2021-24340 - 7.2CVE-2026-84774: WP Statistics Stored XSS
CVE-2026-84774 - 7.2CVE-2026-15780: WP Statistics <= 14.16.8 Stored Cross-Site Scripting
CVE-2026-15780 - 7.2CVE-2026-48839: WP Statistics Stored XSS
CVE-2026-48839
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C