CVE-2026-22850Public exploitNetwork attack vector

Arbitrary SQL execution via poisoned analytics imports

Published Jan 19, 2026 · Updated Jan 19, 2026

Stored SQL injection in ibericode Koko Analytics before 2.1.3 allows remote attackers to execute arbitrary SQL via poisoned analytics values. Data_Export.php interpolates unescaped path and referrer values collected by collect.php into INSERT statements, while Data_Import.php splits uploaded SQL on semicolons and sends every statement to $wpdb->query without validating statement types or tables. The unauthenticated chain requires an administrator to export and reimport poisoned data; users with manage_koko_analytics can upload SQL directly, enabling database reads, writes, or deletion within the WordPress database account's privileges.

CVSS severity8.3
High
EPSS probability0.48%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Stored SQL injection in ibericode Koko Analytics before 2.1.3 allows remote attackers to execute arbitrary SQL via poisoned analytics values. Data_Export.php interpolates unescaped path and referrer values collected by collect.php into INSERT statements, while Data_Import.php splits uploaded SQL on semicolons and sends every statement to $wpdb->query without validating statement types or tables. The unauthenticated chain requires an administrator to export and reimport poisoned data; users with manage_koko_analytics can upload SQL directly, enabling database reads, writes, or deletion within the WordPress database account's privileges.

The record

CVE
CVE-2026-22850
Published
Jan 19, 2026
Updated
Jan 19, 2026
Vendor
ibericode
Product
Koko Analytics
Classifications
CWE-89, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Jan 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.1.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

ibericode · Koko Analyticsversion=< 2.1.3

Published CVSS scores

8.3GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo