CVE-2026-59234: Roskus Prospero Flow CRM · Insecure Direct Object Reference
Affects Roskus Prospero Flow CRMSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 5.5.3 when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.5.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Roskus Prospero Flow CRM to 5.5.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RoskusProspero Flow CRM | Affected
| Fixed in
|
GitHubProspero Flow CRMpkg:github/Prospero Flow CRMOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:roskus:prospero_flow_crm:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict access to the affected endpoint and review user permissions to limit exposure.
Description
Authorization Bypass Through User-Controlled Key (CWE-639) in CalendarDeleteEventController (app/Http/Controllers/Calendar/CalendarDeleteEventController.php), exposed at GET /calendar/event/delete/{id}, in Prospero Flow CRM before 5.5.3 allows a remote, authenticated attacker to delete arbitrary calendar events belonging to other users by manipulating the {id} path parameter, because the delete handler resolves the record with Calendar::find($id)->delete() and performs no ownership check (no user_id/company_id scoping) before deletion. This results in unauthorized destruction of other users' calendar events across the platform.
References
- github.com/Roskus/prospero-flow-crm/commit/8c26eed4d80544c30e55448e12a8e999af6d2b70 (opens in a new tab)
- github.com/Roskus/prospero-flow-crm/releases/tag/v5.5.3 (opens in a new tab)
- secur0.com/en/cna/cve-list/cve-2026-59234-idor-in-prospero-flow-crm-allows-deletion-of-other-users-calendar-events (opens in a new tab)