dbcve.org
Click To ChatWordPress extension · Ninjateam

CVE-2024-49281

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-17
Fix available
A fix is available. Upgrade to 2.3.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Ninja Team Click to Chat – WP Support All-in-One Floating Widget support-chat allows Stored XSS.This issue affects Click to Chat – WP Support All-in-One Floating Widget: from n/a through <= 2.3.3.

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 · moderate confidence

The Ninja Team Click to Chat WordPress plugin (version <= 2.3.3) contains a Stored XSS vulnerability in the support-chat functionality. User-supplied input in the support chat feature is not properly sanitized before being stored and rendered, allowing malicious scripts to persist and execute when other users view the chat. Note: The CVE title references OS Command Injection but the description explicitly indicates Stored XSS.

MitigationUpdate the plugin to the latest version beyond 2.3.3 if a patch is available; otherwise disable the plugin until a secure version is released. Implement proper input validation and output encoding for all user-supplied data in the chat functionality.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Click To ChatWordPress extension
Affected:< 2.3.4

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 Ninjateam Click To Chat plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ninjateam Click To Chat' or check the plugins directory for the ninjateam-click-to-chat folder
    Affected if Plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin > Plugins, find Ninjateam Click To Chat and note the version number displayed, or read the main plugin PHP file header for the Version field
    Affected if Version is 2.3.3 or lower (any version before 2.3.4)
  3. Confirm support-chat functionality is in use
    Review the plugin settings under the plugin's admin menu to see if any chat-related features are enabled, or check for chat-related shortcodes or widgets in use on the site
    Affected if Support chat feature is active or was previously used on the site
  4. Inspect stored chat data for malicious scripts
    Access the WordPress database and query the plugin's chat tables (typically containing 'chat' in the table name) for patterns like <script tags, javascript:, or onload/onerror attributes in the message content
    Affected if Stored chat records contain unsanitized HTML or JavaScript code

You are affected if the Ninjateam Click To Chat plugin version is 2.3.3 or lower and the support-chat feature is or was enabled, as this combination allows stored XSS to persist in chat messages.

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
Upgrade available Upgrade to 2.3.4 or later
Fixed in 2.3.4
Interim mitigation

Update the plugin to the latest version beyond 2.3.3 if a patch is available; otherwise disable the plugin until a secure version is released. Implement proper input validation and output encoding for all user-supplied data in the chat functionality.

Recommended fix High confidence

2.3.4

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find 'Click to Chat – WP Support All-in-One Floating Widget' in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to version 2.3.4
  5. 5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. 6. After updating, verify the plugin version shows 2.3.4 in the plugins list
  7. 7. Test the chat functionality to ensure it continues to work correctly

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

Fix this in Click To Chat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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