CVE-2022-25060

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-02-26. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 40%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

TP-LINK TL-WR840N(ES)_V6.20_180709 was discovered to contain a command injection vulnerability via the component oal_startPing.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
68(Track*)
EG Risk 68/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation48% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
98.5%
KEV
Not listed

Published

February 25, 2022

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jul 19, 2026
No patch confirmed yet.
generic

Notion

https://east-trowel-102.notion.site/CVE-2021-XXXX-Injection-of-commands-through-object-oal_startPing-EN-939c748c5f244504899477114b1ca1cf
generic

Checking your browser...

http://router.com

Vendor Advisories for CVE-2022-25060(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-24 14:15 UTCEPSS rescore
  2. 2026-07-23 14:16 UTCEPSS rescore
  3. 2026-07-23 02:09 UTCEG score recompute
  4. 2026-07-22 22:56 UTCEG score recompute
  5. 2026-07-22 14:06 UTCEPSS rescore
  6. 2026-07-22 14:06 UTCEPSS rescore
  7. 2026-07-21 15:22 UTCEPSS rescore
  8. 2026-07-21 15:22 UTCEPSS rescore
  9. 2026-07-20 17:05 UTCEPSS rescore
  10. 2026-07-19 02:27 UTCEPSS rescore
  11. 2026-07-18 10:02 UTCEPSS rescore
  12. 2026-07-18 10:02 UTCEPSS rescore
  13. 2026-07-16 17:00 UTCEPSS rescore
  14. 2026-07-16 17:00 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 16:56 UTCEPSS rescore
  17. 2026-07-13 22:27 UTCEPSS rescore
  18. 2026-07-13 06:11 UTCEPSS rescore
  19. 2026-07-13 06:11 UTCEPSS rescore
  20. 2026-07-11 08:25 UTCEPSS rescore
  21. 2026-07-09 19:07 UTCEPSS rescore
  22. 2026-07-09 02:55 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  23. 2026-07-09 01:24 UTCMITRE cvelistV5
  24. 2026-07-06 16:25 UTCEPSS rescore
  25. 2026-07-06 16:25 UTCEPSS rescore
Show 59 more
  1. 2026-07-06 02:21 UTCEPSS rescore
  2. 2026-07-05 17:59 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  3. 2026-07-05 16:09 UTCMITRE cvelistV5
  4. 2026-07-01 15:04 UTCEPSS rescore
  5. 2026-06-30 23:20 UTCEPSS rescore
  6. 2026-06-30 23:20 UTCEPSS rescore
  7. 2026-06-28 04:54 UTCEPSS rescore
  8. 2026-06-28 04:54 UTCEPSS rescore
  9. 2026-06-27 03:07 UTCEPSS rescore
  10. 2026-06-25 13:48 UTCEPSS rescore
  11. 2026-06-24 14:03 UTCEPSS rescore
  12. 2026-06-24 14:03 UTCEPSS rescore
  13. 2026-06-23 21:31 UTCEPSS rescore
  14. 2026-06-23 21:31 UTCEPSS rescore
  15. 2026-06-21 01:58 UTCEPSS rescore
  16. 2026-06-21 01:58 UTCEPSS rescore
  17. 2026-06-18 17:51 UTCEPSS rescore
  18. 2026-06-18 17:51 UTCEPSS rescore
  19. 2026-06-17 17:51 UTCEPSS rescore
  20. 2026-06-17 17:51 UTCEPSS rescore
  21. 2026-06-16 17:51 UTCEPSS rescore
  22. 2026-06-15 17:46 UTCEPSS rescore
  23. 2026-06-14 23:15 UTCEPSS rescore
  24. 2026-06-14 23:15 UTCEPSS rescore
  25. 2026-06-13 22:58 UTCEPSS rescore
  26. 2026-06-13 22:58 UTCEPSS rescore
  27. 2026-06-12 23:10 UTCEPSS rescore
  28. 2026-06-12 23:10 UTCEPSS rescore
  29. 2026-06-11 13:58 UTCEPSS rescore
  30. 2026-06-11 13:58 UTCEPSS rescore
  31. 2026-06-10 22:16 UTCEPSS rescore
  32. 2026-06-10 13:20 UTCEPSS rescore
  33. 2026-06-08 14:15 UTCEPSS rescore
  34. 2026-06-08 14:15 UTCEPSS rescore
  35. 2026-06-07 15:23 UTCEPSS rescore
  36. 2026-06-07 15:23 UTCEPSS rescore
  37. 2026-06-05 22:45 UTCEPSS rescore
  38. 2026-06-05 06:09 UTCEPSS rescore
  39. 2026-06-05 06:09 UTCEPSS rescore
  40. 2026-06-04 13:11 UTCEPSS rescore
  41. 2026-06-04 13:11 UTCEPSS rescore
  42. 2026-06-02 20:11 UTCEPSS rescore
  43. 2026-06-02 20:11 UTCEPSS rescore
  44. 2026-06-02 20:11 UTCEPSS rescore
  45. 2026-06-01 13:50 UTCEPSS rescore
  46. 2026-06-01 13:50 UTCEPSS rescore
  47. 2026-06-01 13:50 UTCEPSS rescore
  48. 2026-05-31 00:15 UTCEPSS rescore
  49. 2026-05-31 00:15 UTCEPSS rescore
  50. 2026-05-29 13:42 UTCEPSS rescore
  51. 2026-05-28 13:43 UTCEPSS rescore
  52. 2026-05-28 13:43 UTCEPSS rescore
  53. 2026-05-28 13:43 UTCEPSS rescore
  54. 2026-05-27 13:39 UTCEPSS rescore
  55. 2026-05-27 13:39 UTCEPSS rescore
  56. 2026-05-26 07:17 UTCEPSS rescore
  57. 2026-05-26 07:17 UTCEPSS rescore
  58. 2026-05-26 02:26 UTCEG score recompute
  59. 2026-05-26 02:26 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-25060?
CVE-2022-25060 is a critical vulnerability published on February 25, 2022. TP-LINK TL-WR840N(ES)V6.20180709 was discovered to contain a command injection vulnerability via the component oal_startPing.
When was CVE-2022-25060 disclosed?
CVE-2022-25060 was first published in the National Vulnerability Database on February 25, 2022, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-25060 actively exploited?
CVE-2022-25060 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-25060?
CVE-2022-25060 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-25060?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-25060, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-25060

Explore →

Is Your Infrastructure Affected by CVE-2022-25060?

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

Start Free Scan →Browse All CVEs