Description
The Geeky Bot WordPress plugin before 1.2.8 does not perform an authorization check on one of its AJAX actions, allowing unauthenticated users to retrieve chat-history session metadata including WordPress usernames, user IDs, and timestamps.
Published: 2026-07-31
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability in Geeky Bot allows any unauthenticated visitor to send an AJAX request that returns chat-history session metadata. The response includes WordPress usernames, user IDs, and timestamps, enabling attackers to map user identities and potentially target accounts with phishing or other social engineering attacks. This constitutes a direct exposure of sensitive data that could be leveraged in downstream attack scenarios.

Affected Systems

Any installation of the Geeky Bot WordPress plugin with a version prior to 1.2.8 is affected. The publisher was identified as Unknown:Geeky Bot, and the vulnerability is specific to the AJAX endpoint that delivers chat history. No specific operating system or platform distinctions are listed, so all environments running the plugin before the noted version are impacted.

Risk and Exploitability

Because the plugin performs no authorization check on the AJAX action, the attack path requires only that an unauthenticated user crafts a correct request. The EPSS score is <1%, indicating a low likelihood of exploitation, but the sensitivity of the exposed data, coupled with a CVSS score of 7.5, signifies a high severity. The vulnerability is not listed in the CISA KEV catalog, but it remains a serious privacy concern for site owners.

Generated by OpenCVE AI on August 2, 2026 at 04:29 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest compatible version of Geeky Bot (>=1.2.8) that includes an authorization check for the chat-history AJAX action.
  • Configure WordPress security settings or a firewall rule to block unauthenticated requests to the chat-history endpoint, allowing only logged‑in users to access it.
  • Audit other AJAX functions in the plugin for similar missing authorization checks and address any that are discovered.

Generated by OpenCVE AI on August 2, 2026 at 04:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 31 Jul 2026 21:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 31 Jul 2026 06:30:00 +0000

Type Values Removed Values Added
Description The Geeky Bot WordPress plugin before 1.2.8 does not perform an authorization check on one of its AJAX actions, allowing unauthenticated users to retrieve chat-history session metadata including WordPress usernames, user IDs, and timestamps.
Title GeekyBot < 1.2.8 - Unauthenticated Sensitive Information Exposure via Chat History
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-07-31T19:48:41.603Z

Reserved: 2026-07-08T12:48:56.997Z

Link: CVE-2026-15048

cve-icon Vulnrichment

Updated: 2026-07-31T19:48:36.938Z

cve-icon NVD

Status : Received

Published: 2026-07-31T07:16:26.827

Modified: 2026-07-31T20:16:47.790

Link: CVE-2026-15048

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-02T04:30:13Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor