Skip to main content
VulnerabilityPublished

CVE-2026-77759: Roskus Prospero Flow CRM · Insecure Direct Object Reference

Affects Roskus Prospero Flow CRMSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 5.3.6 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.3.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.3.6.

Affected software

ProductAffectedFixed in
RoskusProspero Flow CRMAffected
  • >=5.0.0 <5.3.6
Fixed in
  • 5.3.6
GitHubProspero Flow CRMpkg:github/Prospero Flow CRMOther threatsAffected
  • >=5.0.0 <5.3.6
Fixed in
  • 5.3.6

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 access to the API to trusted users only and monitor for suspicious access patterns. Avoid exposing the vulnerable API endpoint to untrusted networks.

Description

CVE-2026-77759 is an authorization bypass vulnerability in Roskus Prospero Flow CRM versions 5.0.0 through 5.3.5. It allows an authenticated user to access transaction data belonging to other companies on the same instance by manipulating the transaction ID in the API request. The flaw exists because the transaction API does not enforce company scoping or permission checks when resolving transaction identifiers.

References

Community reviews

Loading reviews…