CVE-2026-3075

Simple Ajax Chat <= 20251121 - Unauthenticated Information Exposure

2026-02-17 00:00
Jakub Herman

Strategic Overview

Status
Patched in 20260217
Affected Plugin
Simple Ajax Chat – Add a Fast, Secure Chat Box
Affected Version
<= 20251121
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-3075
View all Simple Ajax Chat – Add a Fast, Secure Chat Box vulnerabilities

At a glance

CVE-2026-3075 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Simple Ajax Chat WordPress plugin, affecting versions <= 20251121. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 20260217; sites on affected versions should update now. Disclosed February 2026, reported by Jakub Herman.

Vulnerability Overview

The Simple Ajax Chat – Add a Fast, Secure Chat Box plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 20251121. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.

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.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Simple Ajax Chat <= 20251121 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Simple Ajax Chat the fix is 20260217: builds <= 20251121 are affected, anything from 20260217 onward is not.

Remediation

Update to version 20260217, 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: Simple Ajax Chat 20260217 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-3075https://www.wordfence.com/threat-intel/vulnerabilities/id/abc0d9c0-ed5a-4bb8-9ff1-d2833dd04d31https://nvd.nist.gov/vuln/detail/CVE-2026-3075

Related records

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