CVE-2019-9763

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

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

Score 6.1 from GitHub Security Advisory (severity: MODERATE) published 2022-05-24. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2019-19126 (ENISA EUVD) · GHSA-3jf3-xmwv-mv5p (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictMonitorNo fix on record since 2019: if the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system on your normal schedule, or retire the product (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 6.1Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2019 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

An issue was discovered in Openfind Mail2000 6.0 and 7.0 Webmail. XSS can occur via an '
CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/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)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2019. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) on your normal schedule, or retire the product.
EPSS PROB
1.2%
EPSS %ILE
68th
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 (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). 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.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: 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).

No fix has been recorded since the CVE record was published in 2019. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) on your normal schedule, or retire the product.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

June 19, 2019

Last Modified

November 21, 2024

References (3)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 199 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  2. 2026-11-11 16:30 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  3. 2026-11-10 16:34 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  4. 2026-11-09 16:28 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  5. 2026-11-08 16:31 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  6. 2026-11-07 22:46 UTCGHSA enrichmentGHSA-3jf3-xmwv-mv5p · GitHub severity MODERATE · GitHub CVSS 6.1
  7. 2026-11-07 22:46 UTCEchelonGraph re-scored
  8. 2026-11-07 16:32 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  9. 2026-11-06 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  10. 2026-11-05 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  11. 2026-11-04 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  12. 2026-11-03 16:36 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  13. 2026-11-02 16:36 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  14. 2026-10-31 16:28 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  15. 2026-10-30 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  16. 2026-10-29 16:28 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  17. 2026-10-28 16:27 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  18. 2026-10-27 16:27 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  19. 2026-10-26 16:27 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  20. 2026-10-25 18:55 UTCEchelonGraph re-scored
  21. 2026-10-25 16:28 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  22. 2026-10-25 03:15 UTCEchelonGraph re-scored
  23. 2026-10-25 03:14 UTCGHSA enrichmentGHSA-3jf3-xmwv-mv5p · GitHub CVSS 6.1
  24. 2026-10-24 16:28 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  25. 2026-10-23 16:27 UTCEPSS rescoreEPSS 1.2% · 68th percentile
Show 74 more
  1. 2026-10-22 16:28 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  2. 2026-10-21 16:28 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  3. 2026-10-20 16:28 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  4. 2026-10-19 16:27 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  5. 2026-10-18 16:28 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  6. 2026-10-18 09:40 UTCEchelonGraph re-scored
  7. 2026-10-17 16:28 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  8. 2026-10-16 16:32 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  9. 2026-10-15 16:27 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  10. 2026-10-14 16:28 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  11. 2026-10-13 16:28 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  12. 2026-10-12 19:50 UTCEchelonGraph re-scored
  13. 2026-10-12 16:29 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  14. 2026-10-12 00:14 UTCEchelonGraph re-scored
  15. 2026-10-11 13:42 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  16. 2026-10-10 19:56 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  17. 2026-10-09 20:03 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  18. 2026-10-08 16:38 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  19. 2026-10-07 23:43 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  20. 2026-10-06 15:13 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  21. 2026-10-05 17:39 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  22. 2026-10-04 23:18 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  23. 2026-10-03 14:22 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  24. 2026-09-30 14:59 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  25. 2026-09-30 10:30 UTCEchelonGraph re-scored
  26. 2026-09-27 13:40 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  27. 2026-09-26 15:54 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  28. 2026-09-26 00:20 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  29. 2026-09-24 13:59 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  30. 2026-09-22 14:43 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  31. 2026-09-21 20:28 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  32. 2026-09-20 20:11 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  33. 2026-09-19 15:37 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  34. 2026-09-18 19:23 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  35. 2026-09-17 19:22 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  36. 2026-09-16 14:04 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  37. 2026-09-15 03:06 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  38. 2026-09-13 16:42 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  39. 2026-09-12 14:56 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  40. 2026-09-11 14:48 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  41. 2026-09-11 09:32 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  42. 2026-09-07 15:57 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  43. 2026-09-06 13:44 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  44. 2026-09-05 15:24 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  45. 2026-09-04 13:56 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  46. 2026-09-04 05:03 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  47. 2026-09-02 14:08 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  48. 2026-09-01 03:32 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  49. 2026-08-30 19:14 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  50. 2026-08-30 01:18 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  51. 2026-08-28 21:37 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  52. 2026-08-27 14:21 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  53. 2026-08-26 14:42 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  54. 2026-08-25 13:45 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  55. 2026-08-20 22:51 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  56. 2026-08-19 17:00 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  57. 2026-08-18 13:44 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  58. 2026-08-17 13:43 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  59. 2026-08-16 14:52 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  60. 2026-08-16 02:11 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  61. 2026-08-15 01:26 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  62. 2026-08-13 21:57 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  63. 2026-08-12 13:47 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  64. 2026-08-09 13:43 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  65. 2026-08-08 16:33 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  66. 2026-08-07 16:23 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  67. 2026-08-06 13:43 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  68. 2026-08-05 19:14 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  69. 2026-08-04 15:06 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  70. 2026-08-04 10:34 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  71. 2026-08-03 10:32 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  72. 2026-08-02 02:23 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  73. 2026-08-01 04:12 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  74. 2026-07-30 16:24 UTCEPSS rescoreEPSS 1.2% · 65th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-9763?
CVE-2019-9763 is a medium-severity vulnerability; its CVE record was published on June 19, 2019. An issue was discovered in Openfind Mail2000 6.0 and 7.0 Webmail. XSS can occur via an '<object data="data:text/html' substring in an e-mail message (The vendor subsequently patched this).
When was CVE-2019-9763 made public?
CVE-2019-9763 was made public on June 16, 2019: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on June 19, 2019. 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-9763 actively exploited?
CVE-2019-9763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (68th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-9763?
CVE-2019-9763 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2019-9763?
No fix for CVE-2019-9763 has been recorded since its CVE record was published in 2019. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2019-9763?

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

Book a Demo →Browse All CVEs