WPBot – AI ChatBot for Live Support, Lead Generation, AI Services Plugin Vulnerability (CVE-2026-13731)

On this page

Security Alert Summary

The WPBot – AI ChatBot for Live Support, Lead Generation, AI Services plugin for WordPress is vulnerable to stored cross-site scripting (XSS) via the conversation parameter in all versions up to and including 8.4.9. Insufficient input sanitization and output escaping allow unauthenticated attackers to inject arbitrary web scripts that execute when a user views an injected page. An AJAX nonce required to authenticate the save request is publicly emitted on every frontend page via wp_localize_script, making the nonce freely obtainable by anonymous visitors and removing a practical barrier to exploitation.

CVE Details

  • CVE ID: CVE-2026-13731
  • Affected component: WPBot – AI ChatBot for Live Support, Lead Generation, AI Services plugin for WordPress
  • Affected versions: All versions up to and including 8.4.9
  • Published: July 1, 2026, 5:16:18 AM
  • Last modified: July 1, 2026, 1:56:17 PM
  • CVSS v3.1: Base Score 7.2, Severity HIGH, Vector String CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
  • Authentication / privileges / user interaction: Privileges Required: NONE; User Interaction: NONE; Attack Complexity: LOW; Attack Vector: NETWORK; Scope: CHANGED
  • Primary impact: Confidentiality: LOW; Integrity: LOW; Availability: NONE
  • CWE / weakness: CWE-79 (Cross-site Scripting)

Technical Details

This vulnerability is a stored cross-site scripting issue caused by insufficient input sanitization and missing output escaping for data supplied via the conversation parameter. Data submitted to the plugin can be stored and later rendered into pages without proper escaping, allowing attackers to inject arbitrary JavaScript that will run in the context of any user who views the injected page.

The report additionally notes that an AJAX nonce used to authenticate the save request is emitted to the frontend via wp_localize_script on every page. Because that nonce is publicly available to anonymous visitors, it removes a practical barrier that might otherwise limit exploitation, enabling unauthenticated attackers to perform the save operation needed to store the malicious payload.

As reported, exploitation results in script execution in the context of site pages where the injected content is displayed. The primary technical impacts are limited to confidentiality and integrity (both assessed as LOW) rather than availability.

How This Could Impact Your Website

In a typical site scenario, a site owner manages the plugin and several internal staff members and external contributors use the site for support, lead capture, or content updates. An attacker who injects a malicious script into a stored conversation could cause that script to run when staff or contributors view the affected chat or page. Practical consequences include exposure of internal user data such as email addresses, or unauthorized actions performed in the visible interface that could alter content or capture session information.

Those outcomes can increase the risk of targeted phishing or social engineering against staff whose information is exposed. If you’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.

Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributor-level accounts and other accounts with write or content-management privileges.
  • Enforce strong passwords and enable two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins from your site.
  • Monitor site activity and logs for unusual behavior, including unexpected content changes or occurrences of injected scripts.

If you’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.

References