Skip to main content
CVE-2024-8613VulnerabilityPublished Updated

CVE-2024-8613: gaizhenbiao/chuanhuchatgpt · Insecure Direct Object Reference

Affects gaizhenbiao/chuanhuchatgptSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubgaizhenbiao/chuanhuchatgptpkg:github/gaizhenbiao/chuanhuchatgptOther threatsAffected
  • =20240802
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-8613, organizations should first verify if they are using the affected gaizhenbiao/chuanhuchatgpt versions and apply any available patches or updates from the vendor as soon as they are released. In the absence of patches, implement strict access control policies at the application layer, ensuring that session keys or user identifiers are validated against authenticated user identities before granting access to chat histories. Conduct thorough code reviews focusing on session management and authorization logic to identify and remediate similar flaws. Employ network segmentation and restrict access to the chat platform to trusted users and networks only. Enable detailed logging and monitoring of access to chat histories to detect anomalous behavior indicative of exploitation attempts. Educate users about the importance of safeguarding their credentials and session tokens. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block unauthorized access patterns. Finally, prepare incident response plans that include procedures for handling data breaches involving chat history exposure or deletion.

Description

A vulnerability in gaizhenbiao/chuanhuchatgpt version 20240802 allows attackers to access, copy, and delete other users' chat histories. This issue arises due to improper handling of session data and lack of access control mechanisms, enabling attackers to view and manipulate chat histories of other users.

References

Community reviews

Loading reviews…