Authentication bypass via user-controlled object key
Published May 25, 2023 · Updated May 22, 2026
Authorization bypass in CBOT Chatbot Core before 4.0.3.4 and Panel before 4.0.3.7 allows remote authenticated users to evade access checks. The published record identifies an insecure direct object reference driven by a user-controlled key, but it does not disclose the affected request, parameter, or authorization check. Low-privileged network access is required; successful exploitation permits authentication abuse and bypass, while the precise operations exposed remain undisclosed.
Summary
What happened
Authorization bypass in CBOT Chatbot Core before 4.0.3.4 and Panel before 4.0.3.7 allows remote authenticated users to evade access checks. The published record identifies an insecure direct object reference driven by a user-controlled key, but it does not disclose the affected request, parameter, or authorization check. Low-privileged network access is required; successful exploitation permits authentication abuse and bypass, while the precise operations exposed remain undisclosed.
The record
- CVE
- CVE-2023-2883
- Published
- May 25, 2023
- Updated
- May 22, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-639, CAPEC-115, CAPEC-114
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 25, 2023CVE publishedPublication date reported by the CVE source.
- May 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo