ahmadgb GeekyBot Plugin up to 1.2.2 on WordPress ZIP File authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ahmadgb GeekyBot Plugin up to 1.2.2 on WordPress. It has been classified as critical. This issue affects some unknown processing of the component ZIP File Handler. The manipulation leads to authorization. This vulnerability is traded as CVE-2026-5294. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to apply a patch to fix this issue.
Details
A vulnerability was found in ahmadgb GeekyBot Plugin up to 1.2.2 on WordPress. It has been rated as critical. This issue affects an unknown code block of the component ZIP File Handler. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was shared by Di Nhau. It is possible to read the advisory at wordfence.com. The identification of this vulnerability is CVE-2026-5294 since 04/01/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-27193). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector (Wordfence): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Timeline
04/01/2026 CVE reserved05/05/2026 Advisory disclosed
05/05/2026 VulDB entry created
05/05/2026 VulDB entry last update
Sources
Advisory: wordfence.comResearcher: Di Nhau
Status: Confirmed
CVE: CVE-2026-5294 (🔒)
GCVE (CVE): GCVE-0-2026-5294
GCVE (VulDB): GCVE-100-361079
EUVD: 🔒
Entry
Created: 05/05/2026 06:59Updated: 05/05/2026 07:32
Changes: 05/05/2026 06:59 (65), 05/05/2026 07:32 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.