CVE-2026-39619

CRITICALNVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-08. NVD baseline CVSS 9.6; 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

Also known asEUVD-2026-20261 (ENISA EUVD) · GHSA-7gr5-hfgj-rpgg (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 9.6Exploit: None knownExposed 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 (Patchstack) lists priyanshumittal Busiprof versions up to and including 2.5.2 as affected. No release containing a fix is confirmed on record.

Cross-Site Request Forgery (CSRF) vulnerability in priyanshumittal Busiprof busiprof allows Upload a Web Shell to a Web Server.This issue affects Busiprof: from n/a through <= 2.5.2.

CVSS v3
9.6
EG Score
9.6CRITICALmedium 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)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.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 is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
EPSS PROB
0.1%
EPSS %ILE
3rd
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.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

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

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.

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.

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

April 8, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Oct 7, 2026
No fix on record yet.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 74× 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 99 of 298 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 199 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-39619?
CVE-2026-39619 is a critical-severity vulnerability; its CVE record was published on April 8, 2026. Cross-Site Request Forgery (CSRF) vulnerability in priyanshumittal Busiprof busiprof allows Upload a Web Shell to a Web Server.This issue affects Busiprof: from n/a through <= 2.5.2.
When was CVE-2026-39619 made public?
CVE-2026-39619 was made public on April 8, 2026: that is the date its CVE record's CNA, Patchstack, gives for when the vulnerability was made public. The CVE record itself was published on April 8, 2026. EchelonGraph's copy of the record carries a last-modified date of July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-39619 actively exploited?
CVE-2026-39619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-39619?
CVE-2026-39619 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-39619?
No fix for CVE-2026-39619 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (Patchstack) lists priyanshumittal Busiprof versions up to and including 2.5.2 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-39619?

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