CVE-2026-26211

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreMEDIUM confidence

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

Score 4.8 from GitHub Security Advisory published 2026-08-25. A secondary CVSS source baseline 4.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-65620 (ENISA EUVD) · GHSA-5p97-43v8-cjrm (GitHub Security Advisories)Source: ENISA EUVD

4.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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.4%CVSS: 4.8Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists Creativeitem Ekushey Project Manager CRM versions up to and including 5.0 as affected. No release containing a fix is confirmed on record.

Ekushey Project Manager CRM stores the administrator-configured system name and writes it to the login page without output encoding. The value is emitted in three places on that page: the content attribute of the description meta element, the title element, and the text of an h4 element in the page header. The h4 occurrence is parsed as markup, so HTML placed in the system name field is rendered as markup and any event handler it carries runs. The login page is served without authentication, so the stored value executes in the browser of every visitor who loads it, including visitors who are not signed in, within the origin that serves the login form and alongside the credential fields on it. Storing the value requires an administrator session; the resulting script runs for unauthenticated visitors and persists until the setting is changed.

CVSS v3
4.8
EG Score
4.8MEDIUMmedium confidence
EG Risk
38
EG Risk 38/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.
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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
29th
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 (4.8): severity, escalated by confirmed exploitation. This CVE's 4.8 is its impact severity (EG Severity), not escalated.

EG Severity
4.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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: 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 is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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.

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

August 25, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Aug 25, 2026
No fix on record yet.
Web page

Ekushey Project Manager CRM 5.0 Stored XSS via System Name Field | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ekushey-project-manager-crm-5.0-stored-xss-via-system-name-field
Web page

GitHub - LindHunt/CVE-2026-26211: Public disclosure for CVE-2026-26211, a stored XSS vulnerability affecting Ekushey Project Manager CRM v5.0. · GitHub

https://github.com/LindHunt/CVE-2026-26211

Vendor Advisories for CVE-2026-26211(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-26211?
CVE-2026-26211 is a medium-severity vulnerability; its CVE record was published on August 25, 2026. Ekushey Project Manager CRM stores the administrator-configured system name and writes it to the login page without output encoding. The value is emitted in three places on that page: the content attribute of the description meta element, the title element, and the text of an h4 element in the page…
When was CVE-2026-26211 made public?
CVE-2026-26211 was made public on August 25, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-26211 actively exploited?
CVE-2026-26211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-26211?
CVE-2026-26211 has a CVSS base score of 4.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-26211?
No fix for CVE-2026-26211 is confirmed yet. Until one is published, 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 watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists Creativeitem Ekushey Project Manager CRM versions up to and including 5.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-26211 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-26211

Explore →

Is Your Infrastructure Affected by CVE-2026-26211?

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