CVE-2026-40772

GeekyBot — AI Copilot, Chatbot, WooCommerce Lead Gen & Zero-Prompt Content <= 1.2.2 - Unauthenticated Arbitrary File Upload

2026-04-21 00:00
Nguyen Ba Khanh

Strategic Overview

Status
Patched in 1.2.3
Affected Plugin
Geeky Bot – AI Sales Assistant for WooCommerce
Affected Version
<= 1.2.2
CVSS
8.8High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2026-40772
View all Geeky Bot – AI Sales Assistant for WooCommerce vulnerabilities

At a glance

CVE-2026-40772 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Geeky Bot WordPress plugin, affecting versions <= 1.2.2. It carries a CVSS score of 8.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 April 2026, reported by Nguyen Ba Khanh.

Vulnerability Overview

The GeekyBot — AI Copilot, Chatbot, WooCommerce Lead Gen & Zero-Prompt Content plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all versions up to, and including, 1.2.2. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in Geeky Bot <= 1.2.2 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. 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?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Geeky Bot 1.2.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2026-40772https://www.wordfence.com/threat-intel/vulnerabilities/id/93495395-42cc-4787-be95-4691ff77d01bhttps://nvd.nist.gov/vuln/detail/CVE-2026-40772

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C