dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-15291

HIGH · 7.5 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 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 Chat Help – Click to Chat Button & Form plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.1.3 via the REST API endpoints /wp-json/chat-help/v1/leads and /wp-json/chat-help/v1/leads/{id}. This is due to the plugin not performing any authentication and authorization checks. This makes it possible for unauthenticated attackers to extract sensitive data including customer names, email addresses, phone numbers, WhatsApp messages, complete geolocation data (IP addresses, city, country, ISP, coordinates), device fingerprinting information (browser, OS, screen resolution), and WordPress account credentials (user IDs, usernames, emails, names) for logged-in users who submit forms.

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 Chat Help plugin for WordPress exposes sensitive customer and user data through unauthenticated REST API endpoints (/wp-json/chat-help/v1/leads and /wp-json/chat-help/v1/leads/{id}). These endpoints lack authentication and authorization checks, allowing any unauthenticated attacker to retrieve personal information including names, emails, phone numbers, WhatsApp messages, geolocation data, device fingerprints, and WordPress user credentials.

MitigationUpdate the plugin to the latest patched version once available, or deactivate the plugin if not essential. Alternatively, implement proper authentication and authorization checks on the vulnerable REST API endpoints to ensure only authorized users can access lead data.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm Chat Help plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Chat Help' in the list
    Affected if Chat Help plugin appears in the installed plugins list
  2. Check if Chat Help plugin is active
    In the Plugins list, verify whether the Chat Help plugin has the 'Active' status indicator
    Affected if Chat Help plugin is activated on the site
  3. Verify installed version
    Click on the Chat Help plugin name or view its details to see the version number displayed
    Affected if Installed version falls within an affected version range (compare to any official security advisory)
  4. Test unauthenticated access to leads endpoint
    Send a GET request to https://yourdomain.com/wp-json/chat-help/v1/leads using a tool like curl or browser (no authentication required)
    Affected if The endpoint returns HTTP 200 with JSON data containing lead information (names, emails, phone numbers, etc.)
  5. Test unauthenticated access to specific lead endpoint
    Send a GET request to https://yourdomain.com/wp-json/chat-help/v1/leads/1 (or any ID) without authentication
    Affected if The endpoint returns HTTP 200 with detailed lead data including potentially sensitive user information

If the Chat Help plugin is installed and active AND either of the REST API endpoints (/wp-json/chat-help/v1/leads or /wp-json/chat-help/v1/leads/{id}) return data without requiring authentication, the environment is affected by this CVE.

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 plugin to the latest patched version once available, or deactivate the plugin if not essential. Alternatively, implement proper authentication and authorization checks on the vulnerable REST API endpoints to ensure only authorized users can access lead data.

Recommended fix Moderate confidence

Plugin version > 3.1.3 (check WordPress plugin repository for latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Chat Help – Click to Chat Button & Form' plugin
  4. Check the current version - if it is 3.1.3 or earlier, update is needed
  5. Click 'Update Now' or 'Update' to upgrade to the latest version
  6. After update, verify the plugin functions correctly on the site

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 / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15291 — 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-15291 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