CVE-2026-22850: koko-analytics (WordPress plugin) · SQL Injection
Affects koko-analytics (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.4 High : upgrade to 2.1.3 soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.1.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade koko-analytics (WordPress plugin) to 2.1.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ibericodekoko-analytics | Affected
| Fixed in
|
AI-suggested
- Immediately upgrade the Koko Analytics plugin to version 2.1.3 or later, which contains the patch for this vulnerability.
- Restrict access to the WordPress admin dashboard to trusted IPs or via VPN to reduce risk of malicious imports.
- Implement strict file upload controls and validation to prevent unauthorized SQL file uploads, including disabling or limiting the 'manage_koko_analytics' capability to only highly trusted administrators.
- Monitor and audit analytics export/import activities and database queries for suspicious patterns indicative of SQL injection attempts.
- Employ Web Application Firewalls (WAFs) with rules to detect and block SQL injection payloads targeting the tracking endpoint parameters.
- Regularly back up WordPress databases and files to enable rapid recovery in case of compromise.
- Educate administrators on the risks of importing untrusted SQL files and enforce policies requiring verification of exported data before import.
- Consider isolating analytics data storage or using database user accounts with minimal privileges to limit damage from SQL injection.
- Review and harden WordPress security configurations, including disabling unnecessary plugins and enforcing strong authentication.
Description
Koko Analytics is an open-source analytics plugin for WordPress. Versions prior to 2.1.3 are vulnerable to arbitrary SQL execution through unescaped analytics export/import and permissive admin SQL import. Unauthenticated visitors can submit arbitrary path (`pa`) and referrer (`r`) values to the public tracking endpoint in src/Resources/functions/collect.php, which stores those strings verbatim in the analytics tables. The admin export logic in src/Admin/Data_Export.php writes these stored values directly into SQL INSERT statements without escaping. A crafted path such as "),('999','x');DROP TABLE wp_users;-- breaks out of the value list. When an administrator later imports that export file, the import handler in src/Admin/Data_Import.php reads the uploaded SQL with file_get_contents, performs only a superficial header check, splits on semicolons, and executes each statement via $wpdb->query with no validation of table names or statement types. Additionally, any authenticated user with manage_koko_analytics can upload an arbitrary .sql file and have it executed in the same permissive way. Combined, attacker-controlled input flows from the tracking endpoint into exported SQL and through the import execution sink, or directly via malicious uploads, enabling arbitrary SQL execution. In a worst-case scenario, attackers can achieve arbitrary SQL execution on the WordPress database, allowing deletion of core tables (e.g., wp_users), insertion of backdoor administrator accounts, or other destructive/privilege-escalating actions. Version 2.1.3 patches the issue.