Threats Tagged 'cve-2026-19539'
View all threats tagged with 'cve-2026-19539'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-19539'
Click on any threat for detailed analysis and mitigation recommendations
Authorization Bypass Through User-Controlled Key in the ticket management component in Roskus Prospero Flow CRM before 5.4.9 allows authenticated… (CVE-2026-19539)CVE-2026-19539 0 CVE-2026-19539 is an authorization bypass vulnerability in the ticket management component of Roskus Prospero Flow CRM versions before 5.4.9. Authenticated users from any company can access, modify, or delete tickets belonging to other companies without proper authorization checks. This occurs because the application fails to restrict read and save operations to the authenticated user's company, and the delete operation lacks proper request validation. This vulnerability allows unauthorized disclosure and manipulation of sensitive ticket data across company boundaries. Join the discussion | GCVE Database | 08/11/2026, 15:32:39 UTC Added: 08/11/2026, 18:54:04 UTC |
CVE-2026-19539: CWE-862 Missing Authorization in Roskus Prospero Flow CRMCVE-2026-19539 0 Authorization Bypass Through User-Controlled Key in the ticket management component in Roskus Prospero Flow CRM before 5.4.9 allows authenticated users of any company to read the full content (title, description, and attachments) of tickets belonging to another company, to hijack another company's tickets by reassigning their company_id, and to delete another company's tickets without any authorization check, via the ticket's numeric identifier, because the read and save operations retrieve the record without constraining the query to the authenticated user's company, and the delete controller type-hints a generic Illuminate\Http\Request instead of the TicketDeleteRequest that would enforce the required permission. Join the discussion | CVE Database V5 | 08/11/2026, 13:54:05 UTC Added: 08/11/2026, 14:12:16 UTC |
Showing 1 to 2 of 2 results