vciy

CVE-2023-28094

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.

Pega platform clients who are using versions 7.4 through 8.8.x and have upgraded from a version prior to 8.x may be utilizing default credentials.

CVE-2023-280944 of 4 sources documented this
27

rank 27 = 0 + 25 + 0 + 2 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.00530  ·  without this subject the record ranks 27

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.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 27

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

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

$26,400 = $4.99M incident cost x 1 exposure x 0.0053 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.0053EPSSNOT IN KEVas of 2026-09-20
Severity8.1 HIGHreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2023-06-23, 1096 days at 0.01, as of 2026-06-23. 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
Pega8.1 HIGHreceipt
NVD9.8 CRITICALreceipt

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

Running Pegasystems Pega Platform? 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 · no privileges required · no user interaction · high attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-1393 Use of Default Passwordreceipt
Published consequencesCWE-1393: Authentication: 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 inNo fix version in held sources, as the index stood on 23 Jun 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
CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.0053 · top 56% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byPegareceipt
Recorded changes17 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productPegasystems Pega Platformreceipt
Published rangespega platform >= 6.1 <= 8.8.3receipt

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

Unauthenticated network requestno credentials, no interactionPegasystems Pega PlatformCWE-1393 weaknessFull compromise (C/I/A)C:H / I:H / A:Hexploits CWE-1393data compromise

What it is stated by the CNA

Pega platform clients who are using versions 7.4 through 8.8.x and have upgraded from a version prior to 8.x may be utilizing default credentials. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-1393
affected versions
pega platform >= 6.1 <= 8.8.3
also scored by
[email protected] 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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

check it yourself support.pega.com receipt

Movement the material steps

23 Jun 20230.00043
17 Mar 20250.00233 · scoring model v2025.03.14
15 Jun 20260.00444 · scoring model v2026.06.15
23 Jun 20260.0053
Show all 17 observations
23 Jun 20230.00043
4 Jul 20230.00091
28 Jun 20240.00171
24 Jul 20240.00170
2 Dec 20240.00195
12 Jan 20250.00201
17 Mar 20250.00233
19 Mar 20250.00349
29 Mar 20250.00677
30 Mar 20250.00349
15 Apr 20250.00216
18 Nov 20250.00349
21 Nov 20250.00216
17 Mar 20260.0027
18 Apr 20260.00288
15 Jun 20260.00444
23 Jun 20260.0053

17 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.0053Published2023-06-22Index as of2026-06-23

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

Published 2023-06-22 receipt · Index as of 2026-06-23 derived

Siblings and hubs

Records related to this one

Its defect family

pegasystems pega platform

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

Nothing we hold separates this record from the others in its defect family. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

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

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.