Authorization Bypass Through User-Controlled Key in the transaction API in Roskus Prospero
Flow CRM 5.0.0 through 5.3.5 allows an authenticated user to read the transactions of other
companies on the same instance via an incremented identifier in GET /api/transaction/{id},
which is resolved without company scoping and without any permission check.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Roskus Prospero_Flow_Crm
cpe:2.3:a:roskus:prospero_flow_crm:*:*:*:*:*:*:*:*
|
5.0.0
|
5.3.6
|
References 3
https://github.com/Roskus/prospero-flow-crm/commit/980c35ac00e419591a8adc2d1dbc…
4daa8cea-433a-44bd-9456-53b127fc289a
https://github.com/Roskus/prospero-flow-crm/releases/tag/v5.5.3
4daa8cea-433a-44bd-9456-53b127fc289a
https://secur0.com/en/cna/cve-list/cve-2026-77759-idor-missing-authz-prospero-t…
4daa8cea-433a-44bd-9456-53b127fc289a