CVE-2026-59235: CWE-639 Authorization bypass through User-Controlled key in Roskus Prospero Flow CRM
Missing Authorization (CWE-862) in BankAccountListController (app/Http/Controllers/Api/BankAccount/BankAccountListController.php), exposed at GET /api/bank-account, in Prospero Flow CRM <5.5.3, which allows a remote, authenticated attacker holding a low-privileged role (e.g. the "User"/"Usuario" role) to read arbitrary bank account records belonging to their company by sending an authenticated request to the endpoint with a valid bearer token, because the API route is protected only by the auth:api middleware and carries no permission gate, unlike the equivalent web route, which enforces can('read bank'), and the handler resolves records with Account::where('company_id', Auth::user()->company_id)->get(), performing only company scoping and no role or permission check before returning the data. This results in the unauthorized disclosure of sensitive banking information (e.g. IBAN, SWIFT/BIC, account identifiers) to users who should not have access to it.
AI Analysis
Technical Summary
CVE-2026-59235 is an authorization bypass vulnerability (CWE-639) in Prospero Flow CRM's BankAccountListController (app/Http/Controllers/Api/BankAccount/BankAccountListController.php) affecting versions 4.6.0 through before 5.5.3. The GET /api/bank-account endpoint is protected solely by auth:api middleware without enforcing permission checks like can('read bank'), unlike the web route counterpart. The controller filters bank account records only by company_id matching the authenticated user's company, but does not verify the user's role or permissions, allowing low-privileged authenticated users to read arbitrary bank account data belonging to their company. This results in unauthorized disclosure of sensitive banking details.
Potential Impact
An attacker with any authenticated low-privileged user role can retrieve sensitive bank account information (e.g., IBAN, SWIFT/BIC, account identifiers) of their company without proper authorization. This unauthorized data exposure can lead to privacy violations and potential financial risks for the affected company. The vulnerability does not require privilege escalation or user interaction beyond authentication.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict API access to trusted users only and monitor for unusual access patterns. Implement additional permission checks on the /api/bank-account endpoint to enforce role-based access control equivalent to the web route's can('read bank') permission gate.
CVE-2026-59235: CWE-639 Authorization bypass through User-Controlled key in Roskus Prospero Flow CRM
Description
Missing Authorization (CWE-862) in BankAccountListController (app/Http/Controllers/Api/BankAccount/BankAccountListController.php), exposed at GET /api/bank-account, in Prospero Flow CRM <5.5.3, which allows a remote, authenticated attacker holding a low-privileged role (e.g. the "User"/"Usuario" role) to read arbitrary bank account records belonging to their company by sending an authenticated request to the endpoint with a valid bearer token, because the API route is protected only by the auth:api middleware and carries no permission gate, unlike the equivalent web route, which enforces can('read bank'), and the handler resolves records with Account::where('company_id', Auth::user()->company_id)->get(), performing only company scoping and no role or permission check before returning the data. This results in the unauthorized disclosure of sensitive banking information (e.g. IBAN, SWIFT/BIC, account identifiers) to users who should not have access to it.
CVSS v4.0
Score 8.7high
Affected software
pkg:github/Prospero Flow CRMRun 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
CVE-2026-59235 is an authorization bypass vulnerability (CWE-639) in Prospero Flow CRM's BankAccountListController (app/Http/Controllers/Api/BankAccount/BankAccountListController.php) affecting versions 4.6.0 through before 5.5.3. The GET /api/bank-account endpoint is protected solely by auth:api middleware without enforcing permission checks like can('read bank'), unlike the web route counterpart. The controller filters bank account records only by company_id matching the authenticated user's company, but does not verify the user's role or permissions, allowing low-privileged authenticated users to read arbitrary bank account data belonging to their company. This results in unauthorized disclosure of sensitive banking details.
Potential Impact
An attacker with any authenticated low-privileged user role can retrieve sensitive bank account information (e.g., IBAN, SWIFT/BIC, account identifiers) of their company without proper authorization. This unauthorized data exposure can lead to privacy violations and potential financial risks for the affected company. The vulnerability does not require privilege escalation or user interaction beyond authentication.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict API access to trusted users only and monitor for unusual access patterns. Implement additional permission checks on the /api/bank-account endpoint to enforce role-based access control equivalent to the web route's can('read bank') permission gate.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Secur0
- Date Reserved
- 2026-07-03T11:24:39.242Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a57657268715ace4390779d
Added to database: 07/15/2026, 10:48:18 UTC
Last enriched: 07/15/2026, 11:02:30 UTC
Last updated: 07/16/2026, 03:33:56 UTC
Views: 25
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.