dbcve.org
Cbot CoreApplication · Cbot

CVE-2023-2887

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to 4.0.3.4 / 4.0.3.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Authentication Bypass by Spoofing vulnerability in CBOT Chatbot allows Authentication Bypass. This issue affects Chatbot: before Core: v4.0.3.4 Panel: v4.0.3.7.

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

Authentication Bypass by Spoofing vulnerability in CBOT Chatbot allows unauthenticated attackers to bypass authentication mechanisms in the Chatbot Core (before v4.0.3.4) and Panel (before v4.0.3.7) components, potentially gaining unauthorized access to the system.

MitigationUpgrade CBOT Chatbot Core to version 4.0.3.4 or later and Panel to version 4.0.3.7 or later to remediate the authentication bypass vulnerability.

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
Cbot CoreApplication
Affected:< 4.0.3.4
Cbot PanelApplication
Affected:< 4.0.3.7

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
High
Availability
High

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

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. Identify if CBOT Chatbot is installed
    Search for CBOT Chatbot processes or services running on the system. Check for directories or files named 'cbot', 'cbot-core', or 'cbot-panel' in common installation locations.
    Affected if CBOT Chatbot software is found running on the system
  2. Determine Cbot Core version
    Locate the Cbot Core installation and check its version information. Common methods include: looking for a version file, checking the application's about page, or using any available CLI tool with version flag.
    Affected if The installed Cbot Core version is less than 4.0.3.4
  3. Determine Cbot Panel version
    Locate the Cbot Panel installation and check its version information. Common methods include: accessing the Panel's admin interface version display, checking configuration files, or using any available CLI tool with version flag.
    Affected if The installed Cbot Panel version is less than 4.0.3.7
  4. Assess network exposure of Core component
    Verify if the Cbot Core component is accessible over the network (HTTP/HTTPS ports). Check firewall rules and exposed network interfaces.
    Affected if Cbot Core is network-accessible AND version is below 4.0.3.4
  5. Assess network exposure of Panel component
    Verify if the Cbot Panel component is accessible over the network (HTTP/HTTPS ports). Check firewall rules and exposed network interfaces.
    Affected if Cbot Panel is network-accessible AND version is below 4.0.3.7

If either Cbot Core version is below 4.0.3.4 or Cbot Panel version is below 4.0.3.7 and either component is network-accessible, the environment is affected by this authentication bypass vulnerability.

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 4.0.3.4 / 4.0.3.7 or later
Fixed in 4.0.3.44.0.3.7
Interim mitigation

Upgrade CBOT Chatbot Core to version 4.0.3.4 or later and Panel to version 4.0.3.7 or later to remediate the authentication bypass vulnerability.

Recommended fix High confidence

Cbot Core: 4.0.3.4+ | Cbot Panel: 4.0.3.7+

  1. Identify current versions of Cbot Core and Cbot Panel currently deployed
  2. Download Cbot Core version 4.0.3.4 or later from the official vendor source
  3. Download Cbot Panel version 4.0.3.7 or later from the official vendor source
  4. Create a complete backup of the current Cbot installation including database and configuration files
  5. Upgrade Cbot Core to version 4.0.3.4 or later following standard upgrade procedures
  6. Upgrade Cbot Panel to version 4.0.3.7 or later following standard upgrade procedures
  7. Verify that both components are running the fixed versions after upgrade
  8. Test authentication functionality to confirm the vulnerability is remediated

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

Fix this in Cbot Core Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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