LiveActive security incident?Get immediate response
CVE Record

CVE-2023-2886: Cross-Site WebSocket Hijacking in CBOT's Chatbot

Missing Origin Validation in WebSockets vulnerability in CBOT Chatbot allows Content Spoofing Via Application API Manipulation. This issue affects Chatbot: before Core: v4.0.3.4 Panel: v4.0.3.7.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-2886 affects CBOT Chatbot versions before Core v4.0.3.4 and Panel v4.0.3.7. The issue is missing Origin validation in WebSockets, which can allow content spoofing through application API manipulation if a user is tricked into interacting with a malicious site.

Executive priority

Treat as a moderate-priority application integrity issue. Prioritize remediation for internet-facing or broadly accessed chatbot deployments, especially where spoofed content could mislead customers, employees, or operators.

Technical view

The vulnerability is described as Cross-Site WebSocket Hijacking caused by missing WebSocket Origin validation. CVSS 3.1 is 4.3: network exploitable, low complexity, no privileges required, user interaction required, and low integrity impact. Confidentiality and availability impacts are not indicated.

Likely exposure

Organizations using CBOT Chatbot Core before v4.0.3.4 or Panel before v4.0.3.7 may be exposed. Exposure depends on deployment, user access patterns, and whether WebSocket requests are reachable from user browsers.

Exploitation context

No CISA KEV listing or source-bundle evidence indicates active exploitation. The CVSS vector requires user interaction, suggesting a victim would need to visit or interact with attacker-controlled content for abuse to occur.

Researcher notes

Public details are limited to missing WebSocket Origin validation and content spoofing via API manipulation. Do not assume data theft or service disruption from the provided sources. Validate behavior defensively without publishing exploit mechanics.

Mitigation direction

  • Identify CBOT Chatbot Core and Panel deployments.
  • Upgrade Core to v4.0.3.4 or later if affected.
  • Upgrade Panel to v4.0.3.7 or later if affected.
  • Review vendor and government advisories for current guidance.
  • Restrict exposure where possible until versions are confirmed.

Validation and detection

  • Confirm installed Core and Panel versions.
  • Check whether WebSocket endpoints validate trusted Origin values.
  • Review application configuration for allowed origins.
  • Assess browser-accessible routes to CBOT Chatbot services.
  • Document affected instances and remediation status.
Prepared
Confidence
high
Sources
4

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 · low confidence lookup

CWE-1385: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2023-2886 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
4.3 (3.1)
Known Exploited
No
Published

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

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
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-2886Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CBOTChatbot0unaffected
Weakness

CWE details

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

CWE-1385 · source CWE mapping

Missing Origin Validation in WebSockets

Missing Origin Validation in WebSockets represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.