CVE-2026-16548: Chat Widget: Floating Customer Support Button for 30+ Channels, Supporting SMS, Calls, and Chat (WordPress plugin) · Unrestricted File Upload
Affects Chat Widget: Floating Customer Support Button for 30+ Channels, Supporting SMS, Calls, and Chat (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.8.2 when convenient.
Data as of 2 Nov 2026, 22:58 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.8.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade Chat Widget: Floating Customer Support Button for 30+ Channels, Supporting SMS, Calls, and Chat (WordPress plugin) to 1.8.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Chat Widget: Floating Customer Support Button for 30+ Channels, Supporting SMS, Calls, and Chat | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict or monitor file upload endpoints and disable or carefully configure channel response storage or mail-forwarding features to reduce exposure.
Description
The Chat Widget: Floating Customer Support Button for 30+ Channels, Supporting SMS, Calls, and Chat WordPress plugin before 1.8.2 does not validate the type, extension, content, or size of files submitted to its public response endpoint and stores them under the uploads directory, so an unauthenticated user can upload arbitrary files. The original extension is discarded (files are stored under a bare UUID), so this does not yield code execution or stored XSS; impact is bounded to disk consumption and content hosting. The storing path requires the channel's response storage or mail-forwarding to be configured.