{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22850 exists.","fix":"No fix has been published for CVE-2026-22850 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22850 is a high-severity SQL injection vulnerability in ibericode koko-analytics, published on 19 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-22850 and fix it if it is affected.\n\nWhat it is: CVE-2026-22850 is a high-severity SQL injection vulnerability in ibericode koko-analytics, published on 19 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22850 exists.\n\nAffected product: ibericode koko-analytics. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-22850/ (Markdown: https://insights.sbomify.com/CVE-2026-22850/index.md)","id":"CVE-2026-22850","markdown":"https://insights.sbomify.com/CVE-2026-22850/index.md","name":"CVE-2026-22850","record":{"aliases":["GHSA-jgfh-264m-xh3q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress analytics plugin","requires_auth":"none","summary":"Attackers can execute arbitrary SQL via unescaped tracking data or malicious imports, enabling database destruction or admin account creation in Koko Analytics.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"koko_analytics","vendor":"ibericode"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"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-\u003equery 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"SQL injection in koko-analytics","id":"CVE-2026-22850","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"FreeRDP RDPGFX ResetGraphics race leads to use-after-free in SDL client (sdl-\u003eprimary)","id":"CVE-2026-22851"},"packages":[],"prev":{"headline":"Saleor lacks proper HTML sanitization in rich text fields","id":"CVE-2026-22849"},"products":["koko-analytics"],"published":"2026-01-19","related":[{"cvss_score":6.1,"headline":"Koko Analytics \u003c= 1.3.12 - Reflected Cross-Site Scripting","id":"CVE-2024-8662","kev_date_added":null,"published":"2024-09-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-20","vendors":["ibericode"]},"summary":"Attackers can execute arbitrary SQL via unescaped tracking data or malicious imports, enabling database destruction or admin account creation in Koko Analytics.","url":"https://insights.sbomify.com/CVE-2026-22850/"}