dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-13731

HIGH · 7.2 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The WPBot – AI ChatBot for Live Support, Lead Generation, AI Services plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'conversation' parameter in all versions up to, and including, 8.4.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The AJAX nonce required to authenticate the save request is publicly emitted on every frontend page via wp_localize_script, making it freely obtainable by any anonymous visitor and removing any practical barrier to exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WPBot WordPress plugin fails to properly sanitize the 'conversation' parameter on input and escape it on output, allowing stored XSS injection. Additionally, the AJAX nonce required to authenticate save requests is publicly exposed via wp_localize_script on every frontend page, enabling unauthenticated attackers to bypass authentication and inject malicious scripts that execute whenever users access affected pages.

MitigationUpdate the WPBot plugin to a version beyond 8.4.9 which includes proper input sanitization, output escaping, and nonce protection. Until the patch is available, consider disabling the plugin or implementing additional firewall rules at the WAF level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WPBot plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WPBot' in the list, or check the /wp-content/plugins/ directory for a folder named 'wpbot' or similar
    Affected if WPBot plugin is present on the WordPress site
  2. Check installed WPBot version
    In WordPress admin, go to Plugins > Installed Plugins and locate WPBot to view its version number, or inspect the main plugin file (usually wpbot.php) and look for a version comment/constant
    Affected if Version is 8.4.9 or lower
  3. Confirm AJAX endpoint exposure
    View the page source of any frontend page on the site and search for 'wp_localize_script' calls that contain 'ajax nonce' or 'nonce' strings associated with WPBot, or check network requests for admin-ajax.php calls
    Affected if The AJAX nonce is exposed via wp_localize_script on frontend pages (visible in page source)
  4. Verify conversation feature is active
    Check WPBot settings in WordPress admin for any chat/conversation functionality that uses a 'conversation' parameter, or test submitting a chat message through the WPBot interface
    Affected if The conversation/chat feature is enabled and accessible to frontend users

A site is affected if WPBot plugin version 8.4.9 or lower is installed AND the conversation/chat feature is enabled, since the exposed nonce and lack of input sanitization create the stored XSS vector.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WPBot plugin to a version beyond 8.4.9 which includes proper input sanitization, output escaping, and nonce protection. Until the patch is available, consider disabling the plugin or implementing additional firewall rules at the WAF level.

Recommended fix Moderate confidence

Latest version of WPBot plugin (newer than 8.4.9)

  1. 1. Log in to the WordPress admin dashboard.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'WPBot – AI ChatBot for Live Support, Lead Generation, AI Services' plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest patched version.
  5. 5. After updating, verify the plugin version is newer than 8.4.9.
  6. 6. Clear any site caching if applicable.
  7. 7. Test the chat functionality to ensure the plugin still works correctly after the update.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13731 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13731 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data