CVE-2019-2598

HIGHNVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.7 under NVD CVSS v3. EPSS exploit probability: 1.3% (69th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Vulnerability in the PeopleSoft Enterprise PeopleTools component of Oracle PeopleSoft Products (subcomponent: SQR). Supported versions that are affected are 8.55, 8.56 and 8.57. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. While the vulnerability is in PeopleSoft Enterprise PeopleTools, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise PeopleTools accessible data as well as unauthorized access to critical data or complete access to all PeopleSoft Enterprise PeopleTools accessible data. CVSS 3.0 Base Score 8.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N).

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
1.3%
EPSS %ILE
69th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 23, 2019

Last Modified

November 21, 2024

References (1)

Data Freshness Timeline

(refreshed 10× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 160 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 67 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-22 16:28 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  2. 2026-10-21 17:44 UTCEG score recompute
  3. 2026-10-21 17:44 UTCGHSA enrichmentGHSA-pc57-hj73-639x · GitHub severity HIGH
  4. 2026-10-21 16:27 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  5. 2026-10-20 16:28 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  6. 2026-10-19 16:27 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  7. 2026-10-18 16:27 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  8. 2026-10-18 09:46 UTCEG score recompute
  9. 2026-10-17 16:28 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  10. 2026-10-16 16:32 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  11. 2026-10-15 16:27 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  12. 2026-10-14 16:28 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  13. 2026-10-13 16:28 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  14. 2026-10-12 19:55 UTCEG score recompute
  15. 2026-10-12 16:28 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  16. 2026-10-12 00:19 UTCEG score recompute
  17. 2026-10-11 13:42 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  18. 2026-10-10 19:56 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  19. 2026-10-09 20:03 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  20. 2026-10-08 16:37 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  21. 2026-10-07 23:43 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  22. 2026-10-06 15:13 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  23. 2026-10-05 17:39 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  24. 2026-10-04 23:18 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  25. 2026-10-03 14:22 UTCEPSS rescoreEPSS 1.3% · 68th percentile
Show 68 more
  1. 2026-09-30 14:59 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  2. 2026-09-30 10:20 UTCEG score recompute
  3. 2026-09-28 13:46 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  4. 2026-09-27 13:40 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  5. 2026-09-26 15:54 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  6. 2026-09-26 00:20 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  7. 2026-09-24 13:59 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  8. 2026-09-22 14:43 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  9. 2026-09-21 20:28 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  10. 2026-09-20 20:11 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  11. 2026-09-19 15:37 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  12. 2026-09-18 19:23 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  13. 2026-09-17 19:22 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  14. 2026-09-16 14:04 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  15. 2026-09-15 03:06 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  16. 2026-09-13 16:42 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  17. 2026-09-12 14:56 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  18. 2026-09-11 14:48 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  19. 2026-09-11 09:32 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  20. 2026-09-08 21:55 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  21. 2026-09-07 15:57 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  22. 2026-09-06 13:44 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  23. 2026-09-05 15:24 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  24. 2026-09-04 13:56 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  25. 2026-09-02 14:08 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  26. 2026-09-01 03:32 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  27. 2026-08-30 01:18 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  28. 2026-08-27 14:21 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  29. 2026-08-26 14:42 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  30. 2026-08-25 13:45 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  31. 2026-08-19 17:00 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  32. 2026-08-18 13:44 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  33. 2026-08-15 01:26 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  34. 2026-08-13 21:57 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  35. 2026-08-12 13:47 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  36. 2026-08-09 13:43 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  37. 2026-08-08 16:33 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  38. 2026-08-07 16:23 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  39. 2026-08-05 19:13 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  40. 2026-08-04 15:05 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  41. 2026-08-04 10:34 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  42. 2026-08-03 10:32 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  43. 2026-08-02 02:23 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  44. 2026-08-01 04:12 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  45. 2026-07-30 16:24 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  46. 2026-07-30 01:27 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  47. 2026-07-28 15:32 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  48. 2026-07-26 14:51 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  49. 2026-07-25 14:14 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  50. 2026-07-24 14:14 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  51. 2026-07-23 14:15 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  52. 2026-07-23 01:44 UTCEG score recompute
  53. 2026-07-22 22:25 UTCEG score recompute
  54. 2026-07-22 14:05 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  55. 2026-07-21 15:22 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  56. 2026-07-20 17:04 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  57. 2026-07-19 02:26 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  58. 2026-07-18 10:02 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  59. 2026-07-16 16:59 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  60. 2026-07-15 16:55 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  61. 2026-07-15 01:57 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  62. 2026-07-13 22:27 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  63. 2026-07-13 06:10 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  64. 2026-07-12 05:43 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  65. 2026-07-11 08:24 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  66. 2026-07-09 19:06 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  67. 2026-07-08 15:11 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  68. 2026-07-07 13:43 UTCEPSS rescoreEPSS 1.3% · 66th percentile

Frequently asked(5)

What is CVE-2019-2598?
CVE-2019-2598 is a high-severity vulnerability; its CVE record was published on April 23, 2019. Vulnerability in the PeopleSoft Enterprise PeopleTools component of Oracle PeopleSoft Products (subcomponent: SQR). Supported versions that are affected are 8.55, 8.56 and 8.57. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise PeopleSoft…
When was the CVE record for CVE-2019-2598 published?
The CVE record for CVE-2019-2598 was published on April 23, 2019. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2019-2598 actively exploited?
CVE-2019-2598 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (69th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-2598?
CVE-2019-2598 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2019-2598?
A fix for CVE-2019-2598 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-2598

Explore →

Is Your Infrastructure Affected by CVE-2019-2598?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs