# CVE-2023-51371: WordPress Bit Assist Plugin <= 1.1.9 is vulnerable to Cross Site Scripting (XSS)

> An attacker can inject malicious scripts into the Bit Assist chat widget, potentially compromising user sessions or site integrity.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Dec 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-v2xm-vc3c-5672

## What is CVE-2023-51371?

CVE-2023-51371 is a medium-severity cross-site scripting vulnerability in Bit Assist Chat Widget: WhatsApp Chat, Facebook Messenger Chat, Telegram Chat Bubble, Line Messenger, Live Chat Support Chat Button, WeChat, SMS, Call Button, Customer Support Button with floating Chat Widget, published on 29 Dec 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Bit Assist Chat Widget: WhatsApp Chat, Facebook Messenger Chat, Telegram Chat Bubble, Line Messenger, Live Chat Support Chat Button, WeChat, SMS, Call Button, Customer Support Button with floating Chat Widget allows Stored XSS.This issue affects Chat Widget: WhatsApp Chat, Facebook Messenger Chat, Telegram Chat Bubble, Line Messenger, Live Chat Support Chat Button, WeChat, SMS, Call Button, Customer Support Button with floating Chat Widget: from n/a through 1.1.9.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-51371?

It affects 1 product.


Products: Bitapps Bit Assist.

## How do I fix CVE-2023-51371?

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

## Is CVE-2023-51371 being exploited?

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

## Other vulnerabilities in Bit Assist Chat Widget: WhatsApp Chat, Facebook Messenger Chat, Telegram Chat Bubble, Line Messenger, Live Chat Support Chat Button, WeChat, SMS, Call Button, Customer Support Button with floating Chat Widget

- [CVE-2025-0822](https://insights.sbomify.com/CVE-2025-0822/): Bit Assist <= 1.5.2 - Path Traversal to Authenticated (Subscriber+) Arbitrary File Read via fileID Parameter (medium 6.5)
- [CVE-2025-0821](https://insights.sbomify.com/CVE-2025-0821/): Bit Assist <= 1.5.2 - Authenticated (Subscriber+) SQL Injection via id Parameter (medium 6.5)
- [CVE-2024-13791](https://insights.sbomify.com/CVE-2024-13791/): Path traversal in Chat Widget: Floating Customer Support Button for 30+ Channels, Supporting SMS, Calls, and Chat – Bit Assist (medium 4.9)
- [CVE-2023-3667](https://insights.sbomify.com/CVE-2023-3667/): Bit Assist < 1.1.9 - Admin+ Stored Cross-Site Scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51371 and fix it if it is affected.

What it is: CVE-2023-51371 is a medium-severity cross-site scripting vulnerability in Bit Assist Chat Widget: WhatsApp Chat, Facebook Messenger Chat, Telegram Chat Bubble, Line Messenger, Live Chat Support Chat Button, WeChat, SMS, Call Button, Customer Support Button with floating Chat Widget, published on 29 Dec 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-51371 in the wild and no public exploit code.

Affected product: Bit Assist Chat Widget: WhatsApp Chat, Facebook Messenger Chat, Telegram Chat Bubble, Line Messenger, Live Chat Support Chat Button, WeChat, SMS, Call Button, Customer Support Button with floating Chat Widget. 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-2023-51371/ (Markdown: https://insights.sbomify.com/CVE-2023-51371/index.md)
```

## Sources

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

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