CVE-2026-59240

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-49632 (ENISA EUVD) · GHSA-m6x4-f6j4-9qq6 (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to version 5.5.1 or higher."

The vulnerability involves an Insecure Direct Object Reference (IDOR) in the DeleteNotificationController::delete() method at endpoint GET /notification/delete/{id}. The flaw allows any authenticated user, regardless of company or permissions, to delete notifications belonging to any other user in the system. The controller retrieves the target record with Notification::findOrFail($id) and deletes it without validating user_id or company_id ownership, unlike the sibling SetNotificationReadAjaxController, which correctly scopes lookups by Auth::id(). Because notification identifiers are sequential, an attacker can iterate over IDs to systematically delete notifications belonging to any user, denying them visibility of ticket alerts, task assignments, and other system events.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
46
EG Risk 46/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)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
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.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

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

July 27, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
Patch available. Sources: github_commit, github_release.
Web page

CVE-2026-59240 · IDOR in Prospero Flow CRM allows deletion of other users notifications | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-59240-idor-in-prospero-flow-crm-allows-deletion-of-other-users-notifications
GitHub release Patch Available

v5.5.3 - Big security upgrade

Patch available: Roskus/prospero-flow-crm v5.5.3

https://github.com/Roskus/prospero-flow-crm/releases/tag/v5.5.3
GitHub commit Patch Available

commit eaee2ae01870 (Roskus/prospero-flow-crm)

Patch available: Roskus/prospero-flow-crm v5.5.3 (contains commit eaee2ae01870)

https://github.com/Roskus/prospero-flow-crm/commit/eaee2ae018701d116164976cbfa37fa9294ab4cc

Vendor Advisories for CVE-2026-59240(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 9× in last 7d / 46× 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 207 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 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-59240?
CVE-2026-59240 is a medium-severity vulnerability; its CVE record was published on July 27, 2026. The vulnerability involves an Insecure Direct Object Reference (IDOR) in the DeleteNotificationController::delete() method at endpoint GET /notification/delete/{id}. The flaw allows any authenticated user, regardless of company or permissions, to delete notifications belonging to any other user in…
When was CVE-2026-59240 made public?
CVE-2026-59240 was made public on July 27, 2026: that is the date its CVE record's CNA, Secur0, gives for when the vulnerability was made public. The CVE record itself was published on July 27, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-59240 actively exploited?
CVE-2026-59240 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59240?
CVE-2026-59240 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59240?
A fix for CVE-2026-59240 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to version 5.5.1 or higher." The vendor advisories EchelonGraph has for CVE-2026-59240 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59240?

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