CVE-2026-18964: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in premio Floating Chat Widget: Contact Chat Icons, Telegram Chat, Line Messenger, WeChat, Email, SMS, Call Button – Chaty
The Floating Chat Widget: Contact Chat Icons, Telegram Chat, Line Messenger, WeChat, Email, SMS, Call Button – Chaty plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 's' parameter in all versions up to, and including, 3.5.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. WordPress's server-side HTML encoding of the 's' search parameter in the <title> element is bypassed because the browser DOM API decodes HTML entities when jQuery's .text() method reads document.title, returning literal special characters that are then embedded unescaped into the constructed HTML attribute value.
AI Analysis
Technical Summary
CVE-2026-18964 is a reflected cross-site scripting vulnerability in the Floating Chat Widget: Contact Chat Icons, Telegram Chat, Line Messenger, WeChat, Email, SMS, Call Button – Chaty WordPress plugin. The flaw exists in the handling of the 's' parameter, which is not properly sanitized or escaped before being embedded in the page. Although WordPress encodes the 's' parameter in the <title> element, the browser's DOM API decodes these entities when jQuery's .text() method reads document.title, resulting in literal special characters being embedded unescaped into HTML attributes. This enables attackers to inject and execute arbitrary web scripts via crafted URLs.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to execute arbitrary scripts in the context of the affected website. This can lead to partial confidentiality and integrity loss, such as stealing user session data or performing actions on behalf of the user. The vulnerability does not impact availability.
Mitigation Recommendations
No official patch or fix is currently documented for this vulnerability. Users should monitor the vendor's advisory channels for updates. In the meantime, avoid using untrusted input in the 's' parameter or implement custom input validation and output encoding to mitigate the risk.
CVE-2026-18964: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in premio Floating Chat Widget: Contact Chat Icons, Telegram Chat, Line Messenger, WeChat, Email, SMS, Call Button – Chaty
Description
The Floating Chat Widget: Contact Chat Icons, Telegram Chat, Line Messenger, WeChat, Email, SMS, Call Button – Chaty plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 's' parameter in all versions up to, and including, 3.5.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. WordPress's server-side HTML encoding of the 's' search parameter in the <title> element is bypassed because the browser DOM API decodes HTML entities when jQuery's .text() method reads document.title, returning literal special characters that are then embedded unescaped into the constructed HTML attribute value.
CVSS v3.1
Score 6.1medium
Affected software
premio
Floating Chat Widget: Contact Chat Icons, Telegram Chat, Line Messenger, WeChat, Email, SMS, Call Button – Chaty
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-18964 is a reflected cross-site scripting vulnerability in the Floating Chat Widget: Contact Chat Icons, Telegram Chat, Line Messenger, WeChat, Email, SMS, Call Button – Chaty WordPress plugin. The flaw exists in the handling of the 's' parameter, which is not properly sanitized or escaped before being embedded in the page. Although WordPress encodes the 's' parameter in the <title> element, the browser's DOM API decodes these entities when jQuery's .text() method reads document.title, resulting in literal special characters being embedded unescaped into HTML attributes. This enables attackers to inject and execute arbitrary web scripts via crafted URLs.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to execute arbitrary scripts in the context of the affected website. This can lead to partial confidentiality and integrity loss, such as stealing user session data or performing actions on behalf of the user. The vulnerability does not impact availability.
Mitigation Recommendations
No official patch or fix is currently documented for this vulnerability. Users should monitor the vendor's advisory channels for updates. In the meantime, avoid using untrusted input in the 's' parameter or implement custom input validation and output encoding to mitigate the risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-08-05T15:07:52.166Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa379d691cc7f38489ada3a
Added to database: 09/11/2026, 03:47:34 UTC
Last enriched: 09/11/2026, 04:03:03 UTC
Last updated: 09/11/2026, 22:23:26 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.