vciy

CVE-2023-1975

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.

Insertion of Sensitive Information Into Sent Data in answerdev/answer

CVE-2023-19754 of 4 sources documented this
18

rank 18 = 0 + 16 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00586  ·  without this subject the record ranks 18

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.5, 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 18

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

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

$23,400 = $4.99M incident cost x 0.8004932139359172 exposure x 0.00586 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.00586EPSSNOT IN KEVas of 2026-09-20
Severity7.6 HIGHreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2023-04-12, 1160 days at 0.01, as of 2026-06-15. 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
@huntrdev7.6 HIGHreceipt
NVD6.5 MEDIUMreceipt
Scoring standard
@huntrdevCVSS v3.0receipt
NVDCVSS v3.1receipt
What it costs
@huntrdevComplete confidentiality loss; partial integrity and availability lossreceipt
NVDComplete confidentiality lossreceipt

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

Running answerdev/answer? 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 loss; partial integrity and availability lossreceipt
Scored fromCVSS v3.0 · the CNA's vectorreceipt
Weakness classCWE-201 Insertion of Sensitive Information Into Sent Datareceipt
Published consequencesCWE-201: Confidentiality: Read Files or Directories, Read Memory, Read Application Data[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in1.0.8receipt
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 CNA7.6 HIGHreceipt
CVSS, NVD6.5 MEDIUMreceipt
Exploit probability0.00586 · top 53% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned by@huntrdevreceipt
Recorded changes18 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productanswerdev/answerreceipt
Published rangesanswer < 1.0.8receipt
Fixed in1.0.8receipt

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 privilegesanswerdev/answerCWE-201 weaknessConfidentiality lossC:Hexploits CWE-201data compromise

What it is stated by the CNA

Insertion of Sensitive Information Into Sent Data in GitHub repository answerdev/answer prior to 1.0.8. receipt

NVD's analysis a second authority

severity
6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
weakness
CWE-201
affected versions
answer < 1.0.8

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

check it yourself huntr.dev github.com receipt

Movement the material steps

12 Apr 20230.00043
17 Mar 20250.00061 · scoring model v2025.03.14
15 Jun 20260.00586 · scoring model v2026.06.15
Show all 18 observations
12 Apr 20230.00043
19 Apr 20230.00084
11 Mar 20240.00100
17 Apr 20240.00117
13 May 20240.00132
21 Sep 20240.00142
1 Nov 20240.00160
17 Dec 20240.00190
17 Mar 20250.00061
29 Mar 20250.00144
30 Mar 20250.00061
18 Nov 20250.00232
21 Nov 20250.00061
4 Jan 20260.00077
5 Feb 20260.00082
12 Apr 20260.00349
19 Apr 20260.00337
15 Jun 20260.00586

18 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.00586Published2023-04-11Index as of2026-06-15

The record had been public for 3 years, 2 months when this index was last written.

Published 2023-04-11 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2023-1975.

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.