# CVE-2026-92999: Click n Chat 1.0.4 - 1.1.2 - Unauthenticated Lead Data Disclosure via click_n_chat_update_lead_list_export_action


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-q54c-xpfc-w532

## What is CVE-2026-92999?

CVE-2026-92999 is a medium-severity vulnerability in Unknown Click n Chat (Chat Widget Integration), published on 21 Oct 2026. 

### Official description

The Click n Chat (Chat Widget Integration) WordPress plugin before 1.1.3 does not perform any authorization check on a lead-export handler, allowing unauthenticated users to download every captured contact record (names, email addresses and phone numbers).

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

## Which versions are affected by CVE-2026-92999?


## How do I fix CVE-2026-92999?

No fix has been published for CVE-2026-92999 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92999 being exploited?

There is no known exploitation of CVE-2026-92999 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92999 and fix it if it is affected.

What it is: CVE-2026-92999 is a medium-severity vulnerability in Unknown Click n Chat (Chat Widget Integration), published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92999 in the wild and no public exploit code.

Affected product: Unknown Click n Chat (Chat Widget Integration). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92999/ (Markdown: https://insights.sbomify.com/CVE-2026-92999/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92999
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92999
- OSV: https://osv.dev/vulnerability/CVE-2026-92999

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92999/
Summaries are generated and may contain mistakes; the official description above is the record.