GeekyBot <= 1.2.2 - Missing Authorization to Unauthenticated Arbitrary Plugin Installation via 'geekybot_frontendajax' AJAX Action
Strategic Overview
- Status
- Patched in 1.2.3
- Affected Plugin
- Geeky Bot – AI Sales Assistant for WooCommerce
- Affected Version
<= 1.2.2- CVSS
- 9.8Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-5294
At a glance
CVE-2026-5294 is a critical-severity Missing Authorization vulnerability in the Geeky Bot WordPress plugin, affecting versions <= 1.2.2. 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.2.3; sites on affected versions should update now. Disclosed May 2026, reported by kiemtiendinhau.
Vulnerability Overview
The Geeky Bot plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.2.2. This is due to a nopriv AJAX route allowing attacker-controlled model/function dispatch and reaching a plugin installer helper that downloads and unzips attacker-supplied ZIP files into wp-content/plugins/. This makes it possible for unauthenticated attackers to perform arbitrary plugin installation and achieve remote code execution.
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-862: Missing Authorization
Reaching this weakness in Geeky Bot <= 1.2.2 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Geeky Bot the fix is 1.2.3: builds <= 1.2.2 are affected, anything from 1.2.3 onward is not.
Remediation
Update to version 1.2.3, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Geeky Bot 1.2.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Geeky Bot – AI Sales Assistant for WooCommerce
- 8.8CVE-2026-40772: GeekyBot Arbitrary File Upload
CVE-2026-40772 - 7.5CVE-2026-57679: GeekyBot SQL Injection
CVE-2026-57679 - 7.5CVE-2026-3456: GeekyBot SQL Injection
CVE-2026-3456 - 7.5CVE-2026-39519: GeekyBot SQL Injection
CVE-2026-39519 - 7.2CVE-2026-61965: Geeky Bot Stored XSS
CVE-2026-61965 - 7.2CVE-2025-15266: GeekyBot Stored XSS
CVE-2025-15266
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C