CVE-2021-32859

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 published 2023-02-21. NVD baseline CVSS 6.1; sources differ by 0.0.

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

Also known asEUVD-2023-0619 (ENISA EUVD) · GHSA-465f-mxxh-grc4 (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.1Exploit: No code on recordExposed 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).

The Baremetrics date range picker is a solution for selecting both date ranges and single dates from a single calender view. Versions 1.0.14 and prior are prone to cross-site scripting (XSS) when handling untrusted placeholder entries. An attacker who is able to influence the field placeholder when creating a Calendar instance is able to supply arbitrary html or javascript that will be rendered in the context of a user leading to XSS. There are no known patches for this issue.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.5%
EPSS %ILE
45th
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
0.5% within 30 daysSource: FIRST EPSS. 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.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).

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; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

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.

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 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

February 21, 2023

Last Modified

November 21, 2024

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmbaremetrics-calendar—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)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
baremetrics-calendar—
  • every version through 1.0.14: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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 94 of 213 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2021-32859?
CVE-2021-32859 is a medium-severity vulnerability; its CVE record was published on February 21, 2023. The Baremetrics date range picker is a solution for selecting both date ranges and single dates from a single calender view. Versions 1.0.14 and prior are prone to cross-site scripting (XSS) when handling untrusted placeholder entries. An attacker who is able to influence the field placeholder when…
When was the CVE record for CVE-2021-32859 published?
The CVE record for CVE-2021-32859 was published on February 21, 2023. 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-2021-32859 actively exploited?
CVE-2021-32859 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-32859?
CVE-2021-32859 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2021-32859?
A fix for CVE-2021-32859 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-32859

Explore →

Is Your Infrastructure Affected by CVE-2021-32859?

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

Book a Demo →Browse All CVEs