CVE-2026-82911: CWE-352 Cross-Site Request Forgery (CSRF) in Roskus Prospero Flow CRM
Description
Cross-Site Request Forgery (CSRF) in the OrderConfirmController at GET /order/confirm/{order_number} in Roskus Prospero Flow CRM before 5.15.11 allows an unauthenticated attacker to confirm any order on behalf of an authenticated user by directing them to a crafted page. Laravel's VerifyCsrfToken middleware enforces CSRF tokens only on POST, PUT, PATCH, and DELETE requests; the Route::get declaration leaves this state-changing action unprotected. Session cookies configured with SameSite=Lax are automatically included in top-level cross-site navigation, so a single link click triggers OrderConfirmController::confirm() and transitions the target order from pending to confirmed without user authorization. Because order numbers are sequential integers, an attacker can enumerate and confirm all existing orders in a single automated sweep.
CVSS v4.0
Score 5.1medium
Affected software
Roskus
Prospero Flow CRM
pkg:github/Prospero Flow CRMcpe:2.3:a:roskus:prospero_flow_crm:*:*:*:*:*:*:*:*Run 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 involves a CSRF attack vector in Roskus Prospero Flow CRM prior to version 5.15.11. The OrderConfirmController exposes a state-changing action via a GET request, which is not protected by Laravel's VerifyCsrfToken middleware since it only protects POST, PUT, PATCH, and DELETE methods. Because session cookies with SameSite=Lax are sent with top-level cross-site navigation, an attacker can cause an authenticated user to confirm orders by directing them to a malicious link. The sequential nature of order numbers allows automated enumeration and confirmation of all orders without user consent or authentication.
Potential Impact
An attacker can confirm any order on behalf of an authenticated user without their consent by exploiting the CSRF vulnerability. This can lead to unauthorized order confirmations, potentially disrupting order processing and business operations. The vulnerability does not require privileges or user interaction beyond clicking a link, increasing the risk of exploitation. However, there is no indication of further privilege escalation or data disclosure from this vulnerability alone.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid exposing state-changing actions via GET requests and consider implementing additional CSRF protections on such endpoints. Reviewing route definitions to use POST or other protected methods for state changes and enforcing CSRF tokens on all sensitive actions is recommended.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Secur0
- Date Reserved
- 2026-08-31T10:22:08.667Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a9ae95cacd9273b49d35ac2
Added to database: 09/04/2026, 15:53:00 UTC
Last enriched: 09/07/2026, 11:55:02 UTC
Last updated: 10/18/2026, 06:48:20 UTC
Views: 78
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.