CVE-2022-4069

CRITICALNVD 4.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 93% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 4.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized

Also known asEUVD-2022-7393 (ENISA EUVD) · GHSA-p55m-g4m3-qmrp (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 93%
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 93%CVSS: 4.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Cross-site Scripting (XSS) - Generic in GitHub repository librenms/librenms prior to 22.10.0.

CVSS v3
4.8
EG Score
9.0CRITICALhigh confidence
EG Risk
59
EG Risk 59/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)
Severity48% × 45%
Impact severity (EG Severity): CVSS 4.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation93% × 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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 available. Apply it within your standard update timelines.
EPSS PROB
93%
EPSS %ILE
99th
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 (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 4.8 MEDIUM): a likelihood of exploitation, not impact.

EG Severity
4.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
93% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.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).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

November 20, 2022

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Oct 16, 2026
Patch available. Sources: github_commit.
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.dev/bounties/a9925d98-dac4-4c3c-835a-d93aeecfb2c5
GitHub commit

commit 8383376f1355 (librenms/librenms)

Fix landed in librenms/librenms commit 8383376f1355 — awaiting tagged release

https://github.com/librenms/librenms/commit/8383376f1355812e09ec0c2af67f6d46891b7ba7

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerlibrenms/librenms @ 22.10.0 (fixes < 22.10.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
librenms/librenms1.19 ... 22.9.0 (100 versions)
  • every version up to 22.10.0: fixed in 22.10.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× 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.

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. 16 repeat rows among the latest 97 are merged into the row they repeat.

  1. 2026-11-01 20:56 UTCEG score recompute
  2. 2026-11-01 20:56 UTCGHSA enrichmentGHSA-p55m-g4m3-qmrp · GitHub severity MODERATE · GitHub CVSS 4.8
  3. 2026-11-01 08:24 UTCGHSA enrichmentGHSA-p55m-g4m3-qmrp · GitHub severity MODERATE · GitHub CVSS 4.8
  4. 2026-11-01 08:24 UTCEG score recompute
  5. 2026-10-31 18:34 UTCEG score recompute
  6. 2026-10-31 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
  7. 2026-10-30 16:07 UTCEG score recompute
  8. 2026-10-29 13:44 UTCEG score recompute
  9. 2026-10-28 16:28 UTCEPSS rescoreEPSS 93% · 99th percentile
  10. 2026-10-28 11:17 UTCEG score recompute
  11. 2026-10-27 08:21 UTCEG score recompute
  12. 2026-10-25 18:00 UTCEG score recompute
  13. 2026-10-25 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
  14. 2026-10-25 01:20 UTCEG score recompute
  15. 2026-10-23 22:58 UTCEG score recompute
  16. 2026-10-22 20:35 UTCEG score recompute
  17. 2026-10-21 18:10 UTCEG score recompute
  18. 2026-10-21 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
  19. 2026-10-20 15:48 UTCEG score recompute
  20. 2026-10-19 13:23 UTCEG score recompute
  21. 2026-10-18 08:27 UTCEG score recompute
  22. 2026-10-17 06:07 UTCEG score recompute
  23. 2026-10-16 03:44 UTCEG score recompute
  24. 2026-10-15 00:39 UTCEG score recompute
  25. 2026-10-14 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
Show 56 more
  1. 2026-10-13 20:39 UTCEG score recompute
  2. 2026-10-13 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
  3. 2026-10-12 18:08 UTCEG score recompute
  4. 2026-10-11 23:11 UTCEG score recompute
  5. 2026-10-11 13:45 UTCEPSS rescoreEPSS 93% · 99th percentile
  6. 2026-10-09 20:05 UTCEPSS rescoreEPSS 93% · 99th percentile
  7. 2026-10-03 14:23 UTCEPSS rescoreEPSS 93% · 99th percentile
  8. 2026-09-30 20:10 UTCOSV refresh
  9. 2026-09-30 16:04 UTCEG score recompute
  10. 2026-09-26 00:22 UTCEPSS rescoreEPSS 93% · 99th percentile
  11. 2026-09-23 13:45 UTCEPSS rescoreEPSS 93% · 99th percentile
  12. 2026-09-16 05:11 UTCEPSS rescoreEPSS 93% · 99th percentile
  13. 2026-09-15 03:07 UTCEPSS rescoreEPSS 93% · 99th percentile
  14. 2026-09-12 02:40 UTCOSV refresh
  15. 2026-09-06 13:45 UTCEPSS rescoreEPSS 93% · 99th percentile
  16. 2026-09-05 15:25 UTCEPSS rescoreEPSS 93% · 99th percentile
  17. 2026-08-30 19:15 UTCEPSS rescoreEPSS 93% · 99th percentile
  18. 2026-08-28 21:38 UTCEPSS rescoreEPSS 93% · 99th percentile
  19. 2026-08-24 08:27 UTCOSV refresh
  20. 2026-08-21 23:46 UTCEPSS rescoreEPSS 93% · 99th percentile
  21. 2026-08-16 14:53 UTCEPSS rescoreEPSS 93% · 99th percentile
  22. 2026-08-12 13:48 UTCEPSS rescoreEPSS 93% · 99th percentile
  23. 2026-08-08 04:49 UTCOSV refresh
  24. 2026-08-04 15:07 UTCEPSS rescoreEPSS 93% · 99th percentile
  25. 2026-07-30 01:28 UTCEPSS rescoreEPSS 93% · 99th percentile
  26. 2026-07-24 14:15 UTCEPSS rescoreEPSS 93% · 99th percentile
  27. 2026-07-23 14:16 UTCEPSS rescoreEPSS 93% · 99th percentile
  28. 2026-07-23 02:13 UTCEG score recompute
  29. 2026-07-22 21:25 UTCEG score recompute▲ 4.20
  30. 2026-07-22 14:06 UTCEPSS rescoreEPSS 93% · 99th percentile
  31. 2026-07-21 15:23 UTCEPSS rescoreEPSS 93% · 99th percentile
  32. 2026-07-20 17:05 UTCEPSS rescoreEPSS 93% · 99th percentile
  33. 2026-07-16 14:49 UTCOSV refresh
  34. 2026-07-15 16:56 UTCEPSS rescoreEPSS 93% · 99th percentile
  35. 2026-06-29 14:04 UTCEPSS rescoreEPSS 93% · 99th percentile
  36. 2026-06-28 14:06 UTCEPSS rescoreEPSS 93% · 99th percentile
  37. 2026-06-28 13:19 UTCOSV refresh
  38. 2026-06-27 03:07 UTCEPSS rescoreEPSS 93% · 99th percentile
  39. 2026-06-23 21:31 UTCEPSS rescoreEPSS 93% · 99th percentile
  40. 2026-06-22 14:24 UTCEPSS rescoreEPSS 93% · 99th percentile
  41. 2026-06-17 17:51 UTCEPSS rescoreEPSS 93% · 99th percentile
  42. 2026-06-15 17:47 UTCEPSS rescoreEPSS 93% · 99th percentile
  43. 2026-06-13 22:59 UTCEPSS rescoreEPSS 63% · 98th percentile
  44. 2026-06-12 23:10 UTCEPSS rescoreEPSS 63% · 98th percentile
  45. 2026-06-11 13:58 UTCEPSS rescoreEPSS 63% · 98th percentile
  46. 2026-06-11 00:09 UTCOSV refresh
  47. 2026-06-10 13:21 UTCEPSS rescoreEPSS 63% · 98th percentile
  48. 2026-06-08 14:15 UTCEPSS rescoreEPSS 63% · 98th percentile
  49. 2026-06-06 13:46 UTCEPSS rescoreEPSS 63% · 98th percentile
  50. 2026-06-05 22:46 UTCEPSS rescoreEPSS 63% · 98th percentile
  51. 2026-06-05 06:09 UTCEPSS rescoreEPSS 63% · 98th percentile
  52. 2026-06-04 13:11 UTCEPSS rescoreEPSS 63% · 98th percentile
  53. 2026-06-02 20:12 UTCEPSS rescoreEPSS 63% · 98th percentile
  54. 2026-06-01 13:50 UTCEPSS rescoreEPSS 63% · 98th percentile
  55. 2026-05-29 13:43 UTCEPSS rescoreEPSS 63% · 98th percentile
  56. 2026-05-25 11:47 UTCEG score recompute

Frequently asked(5)

What is CVE-2022-4069?
CVE-2022-4069 is a critical-severity vulnerability; its CVE record was published on November 20, 2022. Cross-site Scripting (XSS) - Generic in GitHub repository librenms/librenms prior to 22.10.0.
When was the CVE record for CVE-2022-4069 published?
The CVE record for CVE-2022-4069 was published on November 20, 2022. 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-2022-4069 actively exploited?
CVE-2022-4069 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 93% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-4069?
CVE-2022-4069 has a CVSS v3 base score of 4.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2022-4069?
A fix for CVE-2022-4069 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-4069

Explore →

Is Your Infrastructure Affected by CVE-2022-4069?

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