LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31092: WordPress Click to Chat – WP Support All-in-One Floating Widget plugin <= 2.3.4 - Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') 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.4.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a stored cross-site scripting issue in a WordPress chat widget plugin. A user with some site access may be able to save malicious content that later runs in another user's browser. Business impact is usually moderate, but rises on sites with many contributors or sensitive admin sessions.

Executive priority

Treat as a near-term remediation item, not an emergency, unless the site has many contributors, public registration, or sensitive administrator workflows exposed through WordPress sessions.

Technical view

CVE-2025-31092 affects Ninja Team Click to Chat – WP Support All-in-One Floating Widget, package support-chat, through version 2.3.4. It is CWE-79 stored XSS with CVSS 3.1 score 6.5: network reachable, low complexity, low privileges required, user interaction required, and changed scope.

Likely exposure

Exposure is limited to WordPress sites using the affected support-chat plugin at version 2.3.4 or earlier. Risk is higher where untrusted or numerous low-privilege users can access plugin-related content or settings.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector indicates exploitation requires low privileges and user interaction, so this is not evidenced as mass unauthenticated exploitation from the bundle.

Researcher notes

Evidence supports stored XSS only; no exploit details, patch version, or active exploitation are present in the bundle. Validate exposure by version and privilege paths, then follow vendor or Patchstack guidance rather than assuming a specific fix.

Mitigation direction

  • Inventory WordPress sites for the support-chat plugin and version.
  • Check vendor, WordPress, or Patchstack guidance for a fixed release.
  • Update if a fixed version is documented by official guidance.
  • Disable or remove the plugin where no safe version is available.
  • Restrict low-privilege accounts that can modify chat widget content.
  • Review recent widget and plugin configuration changes.

Validation and detection

  • Confirm whether each WordPress site has support-chat installed.
  • Record installed plugin versions and flag versions <= 2.3.4.
  • Review who can edit plugin settings or widget content.
  • Inspect rendered chat widget pages for unexpected script content.
  • Confirm remediation by verifying updated, disabled, or removed plugin state.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-31092 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2025-31092Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Ninja TeamClick to Chat – WP Support All-in-One Floating Widgetsupport-chat, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.