CVE-2026-59240: CWE-639 Authorization bypass through User-Controlled key in Roskus Prospero Flow CRM
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.
AI Analysis
Technical Summary
This vulnerability is an Insecure Direct Object Reference (IDOR) in the DeleteNotificationController::delete() method at the GET /notification/delete/{id} endpoint in Roskus Prospero Flow CRM 1.0.0. The controller uses Notification::findOrFail($id) to retrieve the notification and deletes it without validating that the notification belongs to the authenticated user or their company. Unlike the related SetNotificationReadAjaxController, which properly scopes notifications by authenticated user ID, this flaw allows any authenticated user to delete notifications of any other user. Because notification IDs are sequential, an attacker can enumerate IDs to delete notifications system-wide, causing denial of visibility to important system events for other users.
Potential Impact
An attacker with any authenticated user account can delete notifications belonging to other users, potentially disrupting communication and visibility of critical system events such as ticket alerts and task assignments. This leads to an authorization bypass and denial of service on notification visibility for affected users. There is no indication of privilege escalation or data disclosure beyond notification deletion.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the notification deletion endpoint to only authorized users and implement server-side validation to ensure that users can only delete notifications they own. Review and update the DeleteNotificationController::delete() method to validate user_id and company_id ownership before deletion.
CVE-2026-59240: CWE-639 Authorization bypass through User-Controlled key in Roskus Prospero Flow CRM
Description
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 v4.0
Score 6.9medium
Affected software
Roskus
Prospero Flow CRM
pkg:github/Prospero Flow CRMRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability is an Insecure Direct Object Reference (IDOR) in the DeleteNotificationController::delete() method at the GET /notification/delete/{id} endpoint in Roskus Prospero Flow CRM 1.0.0. The controller uses Notification::findOrFail($id) to retrieve the notification and deletes it without validating that the notification belongs to the authenticated user or their company. Unlike the related SetNotificationReadAjaxController, which properly scopes notifications by authenticated user ID, this flaw allows any authenticated user to delete notifications of any other user. Because notification IDs are sequential, an attacker can enumerate IDs to delete notifications system-wide, causing denial of visibility to important system events for other users.
Potential Impact
An attacker with any authenticated user account can delete notifications belonging to other users, potentially disrupting communication and visibility of critical system events such as ticket alerts and task assignments. This leads to an authorization bypass and denial of service on notification visibility for affected users. There is no indication of privilege escalation or data disclosure beyond notification deletion.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the notification deletion endpoint to only authorized users and implement server-side validation to ensure that users can only delete notifications they own. Review and update the DeleteNotificationController::delete() method to validate user_id and company_id ownership before deletion.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Secur0
- Date Reserved
- 2026-07-03T11:24:39.242Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a67d32d9c2644c7f8e4ddbd
Added to database: 07/27/2026, 21:52:45 UTC
Last enriched: 07/29/2026, 23:55:19 UTC
Last updated: 09/10/2026, 20:01:51 UTC
Views: 84
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.