CVE-2026-77780: Unvalidated bank account and card foreign keys in the Prospero Flow CRM transaction save endpoint allow cross-tenant disclosure of banking identifiers
Authorization Bypass Through User-Controlled Key in the transaction save endpoint in Roskus Prospero Flow CRM 4.9.1 through 5.14.0 allows a user with transaction and accounting creation permissions to disclose another company's bank account name, bank name and card last four digits via a bankaccountid or bankcardid belonging to that company in POST /transaction/save, which is persisted and rendered without any company ownership check.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Prospero Flow CRMto a version that resolves this vulnerability.Fixed in 5.14.2
Event History
Frequently Asked Questions
Who can exploit this issue?
A user must have permissions to create transactions and accounting records. The issue is exploitable when that user can supply a bank_account_id or bank_card_id associated with another company.
What information can be disclosed across tenants?
The affected transaction can expose another company's bank account name, bank name, and the last four digits of a card. The supplied foreign key is persisted and later rendered without a company ownership check.
Which deployments are affected?
Prospero Flow CRM versions 4.9.1 through 5.14.0 are affected. The vulnerable behavior is in POST /transaction/save.
How can I check for potential exploitation?
Review transaction records created through POST /transaction/save for bank_account_id or bank_card_id values that belong to a different company than the transaction. Such cross-company references indicate that banking identifiers may have been disclosed.