vciy

CVE-2024-9216

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Authentication Bypass in gaizhenbiao/ChuanhuChatGPT

CVE-2024-92164 of 4 sources documented this
22

rank 22 = 0 + 20 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00611  ·  without this subject the record ranks 22

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.1, from the CNA  ·  without this subject the record ranks 2

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 22

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 20

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 22

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$26,900over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$26,900 = $4.99M incident cost x 0.8814887365328109 exposure x 0.00611 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00611EPSSNOT IN KEVas of 2026-09-20
Severity8.1 HIGHreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-03-20, 514 days at 0.01, as of 2026-08-16. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running gaizhenbiao/chuanhuchatgpt? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality and integrity lossreceipt
Scored fromCVSS v3.0 · the CNA's vectorreceipt
Weakness classCWE-304 Missing Critical Step in Authenticationreceipt
Published consequencesCWE-304: Access Control, Integrity, Confidentiality: Bypass Protection Mechanism, Gain Privileges or Assume Identity, Read Application Data, Execute Unauthorized Code or Commands[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 16 Aug 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA8.1 HIGHreceipt
Exploit probability0.00611 · top 52% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned by@huntr_aireceipt
Recorded changes31 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productgaizhenbiao/chuanhuchatgptreceipt
Published rangesgaizhenbiao chuanhuchatgpt 2024-12-04receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Network requestrequires low privilegesgaizhenbiao/chuanhuchatgptCWE-304 weaknessConfidentiality and integrity lossC:H / I:Hexploits CWE-304data compromise

What it is stated by the CNA

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. receipt

NVD's analysis a second authority

weakness
CWE-304
affected versions
gaizhenbiao chuanhuchatgpt 2024-12-04
also scored by
[email protected] 8.1 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

check it yourself huntr.com receipt

Movement the material steps

20 Mar 20250.00055
15 Jun 20260.0056 · scoring model v2026.06.15
16 Aug 20260.00611
Show all 31 observations
20 Mar 20250.00055
21 Mar 20250.00048
22 Mar 20250.00055
23 Mar 20250.00046
26 Mar 20250.00047
29 Mar 20250.00028
30 Mar 20250.00047
14 Apr 20250.0005
21 Apr 20250.00057
1 May 20250.00105
27 May 20250.00155
20 Jul 20250.00192
2 Aug 20250.00194
16 Aug 20250.0011
17 Aug 20250.00122
28 Aug 20250.00134
14 Oct 20250.00113
24 Oct 20250.00098
18 Nov 20250.00173
21 Nov 20250.00098
23 Nov 20250.0008
4 Dec 20250.00107
14 Dec 20250.0011
4 Jan 20260.00119
14 Jan 20260.00125
28 Apr 20260.00226
30 Apr 20260.00173
15 Jun 20260.0056
21 Jun 20260.00581
24 Jul 20260.00585
16 Aug 20260.00611

31 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00611Published2025-03-20Index as of2026-08-16

The record had been public for 1 year, 4 months when this index was last written.

Published 2025-03-20 receipt · Index as of 2026-08-16 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2024-9216.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.