CVE-2018-0422

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

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

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.3EG
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.1%CVSS: 7.3Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2018 — use a compensating control (WAF / firewall / segmentation) and check the vendor's advisory.

A vulnerability in the folder permissions of Cisco Webex Meetings client for Windows could allow an authenticated, local attacker to modify locally stored files and execute code on a targeted device with the privilege level of the user. The vulnerability is due to folder permissions that grant a user the permission to read, write, and execute files in the Webex folders. An attacker could exploit this vulnerability to write malicious files to the Webex client directory, affecting all other users of the targeted device. A successful exploit could allow a user to execute commands with elevated privileges. Attacks on single-user systems are less likely to occur, as the attack must be carried out by the user on the user's own system. Multiuser systems have a higher risk of exploitation because folder permissions have an impact on all users of the device. For an attacker to exploit this vulnerability successfully, a second user must execute the locally installed malicious file to allow remote code execution to occur.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/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)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 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: No fix has been recorded since the CVE record was published in 2018. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and check the vendor's advisory for a fix.
EPSS PROB
1.1%
EPSS %ILE
64th
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 (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% 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).

No fix has been recorded since the CVE record was published in 2018. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and check the vendor's advisory for a fix.

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

October 5, 2018

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 10× in last 7d / 33× 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 86 of 161 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. 14 repeat rows among the latest 100 are merged into the row they repeat. The 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-0422?
CVE-2018-0422 is a high-severity vulnerability; its CVE record was published on October 5, 2018. A vulnerability in the folder permissions of Cisco Webex Meetings client for Windows could allow an authenticated, local attacker to modify locally stored files and execute code on a targeted device with the privilege level of the user. The vulnerability is due to folder permissions that grant a…
When was CVE-2018-0422 made public?
CVE-2018-0422 was made public on September 5, 2018: that is the date its CVE record's CNA, Cisco Systems, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 5, 2018. 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-2018-0422 actively exploited?
CVE-2018-0422 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-0422?
CVE-2018-0422 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2018-0422?
No fix for CVE-2018-0422 has been recorded since its CVE record was published in 2018. Restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and check the vendor's advisory for a fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-0422

Explore →

Is Your Infrastructure Affected by CVE-2018-0422?

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

Book a Demo →Browse All CVEs