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.
Published: 2026-09-04
Score: 5.1 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A Cross‑Site Request Forgery flaw in the Prospero Flow CRM OrderConfirmController allows an attacker who does not need to authenticate to confirm any order on behalf of an authenticated user by simply visiting a crafted page. The vulnerability arises because Laravel’s CSRF middleware protects only POST, PUT, PATCH, and DELETE verbs, leaving the GET route that changes order state unguarded. Session cookies set with SameSite=Lax are sent automatically during regular cross‑site navigation, enabling a single link click to trigger the confirmation action and move an order from pending to confirmed without user knowledge. Since order numbers are sequential, an attacker can enumerate and confirm every existing order in a single automated sweep.

Affected Systems

The flaw affects Roskus Prospero Flow CRM versions earlier than 5.15.11. Upgrading to 5.15.11 or later from the main branch applies the fix; no earlier tagged release contains the patch.

Risk and Exploitability

The CVSS score of 5.1 classifies the vulnerability as medium severity, and the EPSS and KEV information are unavailable or negative, indicating no known widespread exploitation. Nevertheless, the attack requires that a user visits a malicious or maliciously modified page to trigger the GET request, making phishing or social engineering plausible vectors. An attacker could exploit the flaw without needing any additional privileges on the system, and by leveraging sequential order numbers, could potentially compromise all orders in the application.

Generated by OpenCVE AI on September 4, 2026 at 16:35 UTC.

Remediation

Vendor Solution

Upgrade to 5.15.11 or later from the main branch; no tagged release carries the fix.


OpenCVE Recommended Actions

  • Upgrade to version 5.15.11 or later from the main branch; no tagged release contains the fix.
  • Implement CSRF protection on the GET order confirmation endpoint so that only requests with a valid CSRF token are processed.
  • Configure session cookies with SameSite=Strict or use secure, same‑site enforcement to prevent automatic inclusion of the authentication cookie in cross‑site requests.
  • Monitor the system for abnormal order confirmation events to detect any accidental or malicious usage of the vulnerable endpoint.

Generated by OpenCVE AI on September 4, 2026 at 16:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 15:45:00 +0000

Type Values Removed Values Added
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.
Title CSRF in Prospero Flow CRM order confirmation allows unauthorized order state changes
First Time appeared Roskus
Roskus prospero Flow Crm
Weaknesses CWE-352
CPEs cpe:2.3:a:roskus:prospero_flow_crm:*:*:*:*:*:*:*:*
Vendors & Products Roskus
Roskus prospero Flow Crm
References
Metrics cvssV4_0

{'score': 5.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Roskus Prospero Flow Crm
cve-icon MITRE

Status: PUBLISHED

Assigner: Secur0

Published:

Updated: 2026-09-04T15:33:44.562Z

Reserved: 2026-08-31T10:22:08.667Z

Link: CVE-2026-82911

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T16:18:16.313

Modified: 2026-09-04T16:18:16.313

Link: CVE-2026-82911

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T16:45:05Z

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)