CVE Catalog

CVE-2026-59240

MediumCVSS 6.9
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.48%

41th percentile - higher than 41% of all known CVEs

Summary

IDOR vulnerability in the `DeleteNotificationController::delete()` method at endpoint `GET /notification/delete/{id}`. An authenticated user can delete notifications of any other user without ownership verification, as the controller does not check `user_id` or `company_id`. Notification IDs are sequential, allowing iteration and systematic deletion.

Risk Assessment

The risk is that any authenticated user can delete notifications of other users, potentially leading to loss of important alerts, tasks, and other system events.

Recommendation

Immediately update the software to a version that includes a fix verifying notification ownership before deletion.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS