vciy

CVE-2023-21887

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.

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: GIS)

CVE-2023-218874 of 4 sources documented this
36

rank 36 = 22 + 12 + 0 + 2 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.43403  ·  without this subject the record ranks 14

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 4.9, from the CNA  ·  without this subject the record ranks 24

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 36

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.33Mover the next 30 days, if this record is yours
Movement+$1.24Mon 2025-11-21, the last material move, 9 months before this reading
Basisassumeda published average, not your estate

$1.33M = $4.99M incident cost x 0.6121449559255632 exposure x 0.43403 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.43403EPSSNOT IN KEVas of 2026-09-20
Severity4.9 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseno fix version held
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-11-21, 274 days at 0.43, as of 2026-08-22. 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 Oracle Corporation MySQL Server? 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 · high privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classNo CWE mapping in held sources.

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 22 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: Proof-of-concept published · 1 public repository, 2024-01-19.

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

Authority who says so

CVSS, the CNA4.9 MEDIUMreceipt
Exploit probability0.43403 · top 1% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byoraclereceipt
Recorded changes28 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productOracle Corporation MySQL Serverreceipt
Published rangesoracle mysql >= 8.0.0 <= 8.0.31receipt

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.

What it is stated by the CNA

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: GIS). Supported versions that are affected are 8.0.31 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). receipt

NVD's analysis a second authority

affected versions
oracle mysql >= 8.0.0 <= 8.0.31
also scored by
[email protected] 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

check it yourself oracle.com receipt

Dated events

2025-03-17EPSS moved 0.00 to 0.722026-06-15EPSS moved 0.49 to 0.43

Movement the material steps

18 Jan 20230.00885
7 Mar 20234.4e-4 · scoring model v2023.03.01
17 Mar 20250.71544 · crossed 0.10 and 0.50 · scoring model v2025.03.14
28 Mar 20250.57849
29 Mar 20250.75242
30 Mar 20250.57849
30 Jul 20250.45813 · crossed 0.50
18 Nov 20250.0883 · crossed 0.10
21 Nov 20250.49353 · crossed 0.10
15 Jun 20260.43131 · scoring model v2026.06.15
22 Aug 20260.43403

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 25 observations
18 Jan 20230.00885
7 Mar 20234.4e-4
8 Mar 20230.00044
24 Jan 20240.00053
9 Aug 20240.00059
17 Dec 20240.00045
17 Mar 20250.71544
19 Mar 20250.75242
20 Mar 20250.71544
27 Mar 20250.75242
28 Mar 20250.57849
29 Mar 20250.75242
30 Mar 20250.57849
28 Jul 20250.59647
30 Jul 20250.45813
1 Oct 20250.47973
27 Oct 20250.45813
28 Oct 20250.47973
13 Nov 20250.49353
18 Nov 20250.0883
21 Nov 20250.49353
27 Dec 20250.47202
28 Dec 20250.49353
15 Jun 20260.43131
22 Aug 20260.43403

25 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.43403Published2023-01-17Public PoC2024-01-19Index as of2026-08-22

Exploit probability more than doubled between 2025-11-18 and 2025-11-21 (0.0883 → 0.49353) and the record had been public for 3 years, 7 months when this index was last written.

Published 2023-01-17 receipt · Public PoC 2024-01-19 receipt · Index as of 2026-08-22 derived

Siblings and hubs

Records related to this one

Browse the index from here

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

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.