vciy

CVE-2024-8613

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.

Improper Access Control in gaizhenbiao/chuanhuchatgpt

CVE-2024-86134 of 4 sources documented this
24

rank 24 = 0 + 22 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00578  ·  without this subject the record ranks 24

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.8, from NVD  ·  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 24

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$25,400over 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

$25,400 = $4.99M incident cost x 0.8814887365328109 exposure x 0.00578 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.00578EPSSNOT IN KEVas of 2026-09-20
Severity8.1 HIGHreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-03-20, 535 days at 0.01, as of 2026-09-06. 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

Sources disagree here.

Severity score
@huntr_ai8.1 HIGHreceipt
NVD8.8 HIGHreceipt
Scoring standard
@huntr_aiCVSS v3.0receipt
NVDCVSS v3.1receipt
What it costs
@huntr_aiComplete confidentiality and integrity lossreceipt
NVDComplete confidentiality, integrity and availability lossreceipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

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-639 Authorization Bypass Through User-Controlled Keyreceipt
Published consequencesCWE-639: Access Control: Bypass Protection Mechanism; Access Control: Gain Privileges or Assume Identity[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in20240918receipt
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
CVSS, NVD8.8 HIGHreceipt
Exploit probability0.00578 · top 54% 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 20240802receipt
Fixed in20240918receipt

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-639 weaknessConfidentiality and integrity lossC:H / I:Hexploits CWE-639data compromise

What it is stated by the CNA

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

NVD's analysis a second authority

severity
8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-639
affected versions
gaizhenbiao chuanhuchatgpt 20240802

The CNA scored it 8.1 and NVD 8.8. Both are shown because both were published; we do not pick one.

check it yourself huntr.com github.com receipt

Movement the material steps

20 Mar 20250.00031
15 Jun 20260.00512 · scoring model v2026.06.15
6 Sep 20260.00578
Show all 31 observations
20 Mar 20250.00031
21 Mar 20250.00027
22 Mar 20250.00031
23 Mar 20250.00026
26 Mar 20250.00029
29 Mar 20250.00024
30 Mar 20250.00029
21 Apr 20250.00033
27 May 20250.00038
16 Jul 20250.00039
20 Jul 20250.00051
16 Aug 20250.0003
17 Aug 20250.00033
28 Aug 20250.00039
14 Oct 20250.00044
17 Oct 20250.00046
18 Oct 20250.00044
24 Oct 20250.00049
18 Nov 20250.00085
21 Nov 20250.00049
23 Nov 20250.00054
4 Dec 20250.00065
14 Dec 20250.00067
4 Jan 20260.00072
14 Jan 20260.0008
28 Apr 20260.00148
30 Apr 20260.00252
15 Jun 20260.00512
21 Jun 20260.0055
16 Aug 20260.00574
6 Sep 20260.00578

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.00578Published2025-03-20Index as of2026-09-06

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

Published 2025-03-20 receipt · Index as of 2026-09-06 derived

Siblings and hubs

Records related to this one

Browse the index from here

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

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.