# CVE-2026-127219: WPChat WordPress Plugin < 1.4.6 Broken Access Control via claim-offer REST Endpoint

> Unauthenticated attackers can register attacker-controlled emails on WordPress sites using WPChat, corrupting the site's identity.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-crxm-rp4p-rj5r

## What is CVE-2026-127219?

CVE-2026-127219 is a medium-severity missing authorization vulnerability in Syed Balkhi WPChat – Live Chat & Messaging Widget for Customer Support, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WPChat plugin for WordPress before 1.4.6 contains a broken access control vulnerability that allows unauthenticated remote attackers to invoke the admin claim-offer action by reusing the publicly exposed wpchat_frontend nonce without any capability check. Attackers can call SmartSearchManagerService::claimOffer() via POST /wp-json/wpchat/v1/smart-search/claim-offer to register an attacker-controlled email against the site's domain using the site's stored api_token, corrupting the WPChat account and newsletter identity bound to the installation.

Weakness: CWE-862 (Missing Authorization)

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-127219 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-127219 is a medium-severity missing authorization vulnerability in Syed Balkhi WPChat – Live Chat & Messaging Widget for Customer Support, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-127219 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Syed Balkhi WPChat – Live Chat & Messaging Widget for Customer Support. 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-127219/ (Markdown: https://insights.sbomify.com/CVE-2026-127219/index.md)
```

## Sources

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

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