CVE-2024-9216 json
Authentication Bypass in gaizhenbiao/ChuanhuChatGPT
published last yr. modified 4mo ago also PYSEC-2025-97 , EUVD-2025-6872
- cvss
- 8.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
An authentication bypass vulnerability exists in gaizhenbiao/ChuanhuChatGPT, as of commit 3856d4f, allowing any user to read and delete other users' chat history. The vulnerability arises because the username is provided via an HTTP request from the client side, rather than being read from a secure source like a cookie. This allows an attacker to pass another user's username to the get_model function, thereby gaining unauthorized access to that user's chat history.
Is CVE-2024-9216 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- huntr.com https://huntr.com/bounties/21e54c3f-e2d7-423b-9890-1f0cb99af4dd referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | chuanhuchatgpt | <=2024-12-04 |
no fix listed |
Affected products
- gaizhenbiao gaizhenbiao/chuanhuchatgpt
Classification
- Weakness
-
- CWE-304 Missing Critical Step in Authentication
References
-
huntr.com
/bounties/21e54c3f-e2d7-423b-9890-1f0cb99af4dd
exploit, third-party-advisory, evidence
Sources
- CVE List CVE-2024-9216
- NVD CVE-2024-9216
- OSV PYSEC-2025-97
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.