CVE-2025-15266
Unknown Unknown - Not Provided
Stored XSS in GeekyBot WordPress Plugin Allows Admin Hijacking

Publication date: 2026-01-14

Last updated on: 2026-04-08

Assigner: Wordfence

Description
The GeekyBot β€” Generate AI Content Without Prompt, Chatbot and Lead Generation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the chat message field in all versions up to, and including, 1.1.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator accesses the Chat History page.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-14
Last Modified
2026-04-08
Generated
2026-05-07
AI Q&A
2026-01-14
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
ahmadgb geeky_bot to 1.1.7 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the GeekyBot WordPress plugin (versions up to and including 1.1.7). It occurs because the plugin does not properly sanitize or escape input in the chat message field, allowing unauthenticated attackers to inject malicious scripts. These scripts execute when an administrator views the Chat History page.


How can this vulnerability impact me? :

An attacker can exploit this vulnerability to execute arbitrary scripts in the context of the administrator's browser. This can lead to theft of sensitive information, session hijacking, or unauthorized actions performed with administrator privileges, potentially compromising the entire WordPress site.


What immediate steps should I take to mitigate this vulnerability?

Immediate steps include disabling or uninstalling the GeekyBot plugin if it is installed, especially since the plugin has been closed as of January 12, 2026, pending a full review. Avoid using versions up to and including 1.1.7, as they are vulnerable. Monitor for updates or patches from the plugin author or WordPress.org before re-enabling the plugin. [2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart