CVE-2026-77780: Roskus Prospero Flow CRM · Insecure Direct Object Reference
Affects Roskus Prospero Flow CRMSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 5.14.2 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.14.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Roskus Prospero Flow CRM to 5.14.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RoskusProspero Flow CRM | Affected
| Fixed in
|
GitHubProspero Flow CRMpkg:github/Prospero Flow CRMOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict transaction and accounting creation permissions to trusted users only and monitor for suspicious activity related to transaction save operations. Implement additional access control checks at the application level if possible to verify company ownership before processing bank account or card identifiers.
Description
CVE-2026-77780 is an authorization bypass vulnerability in Roskus Prospero Flow CRM versions 4.9.1 through before 5.14.2. It allows a user with transaction and accounting creation permissions to access sensitive bank account information of other companies by supplying a bank_account_id or bank_card_id in the transaction save endpoint. The sensitive data disclosed includes bank account name, bank name, and the last four digits of the card. This occurs because the application does not verify company ownership before persisting and rendering this information.