CVE-2026-59240

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

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

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.9(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity69% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

July 27, 2026

Last Modified

July 28, 2026

Advisory Details (3)

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

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 8× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-28 15:42 UTCEG score recompute
  2. 2026-07-28 15:42 UTCGHSA enrichment
  3. 2026-07-28 15:37 UTCEPSS rescore
  4. 2026-07-28 14:42 UTCEG score recompute
  5. 2026-07-28 14:42 UTCGHSA enrichment
  6. 2026-07-27 22:25 UTCEG score recompute
  7. 2026-07-27 21:50 UTCEG score recompute
  8. 2026-07-27 21:49 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59240?
CVE-2026-59240 is a medium vulnerability 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 disclosed?
CVE-2026-59240 was first published in the National Vulnerability Database on July 27, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59240 actively exploited?
CVE-2026-59240 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.9% of all scored CVEs.
What is the CVSS score of CVE-2026-59240?
CVE-2026-59240 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-59240?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59240, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs