Skip to main content
VulnerabilityPublished

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

Affects prospero-flow-crmSource GCVE Database

0
Compare
Authoritative record:CVE-2026-77759· High 8.7

Not known to be exploited · CVSS 8.7 High.

Data as of 19 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.
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 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubroskus/prospero-flow-crmpkg:github/roskus/prospero-flow-crmOther threatsAffected
  • >=5.0.0 <=5.3.5
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, restrict access to the transaction API to trusted users only and monitor for suspicious activity related to transaction ID enumeration. Implement additional access controls or API gateway rules to enforce company scoping if possible.

Description

An authorization bypass vulnerability exists in Roskus Prospero Flow CRM versions 5.0.0 through 5.3.5. An authenticated user can access transactions belonging to other companies on the same instance by incrementing the transaction identifier in the API endpoint GET /api/transaction/{id}. This occurs because the transaction API does not enforce company scoping or perform permission checks on the requested transaction ID.

References

Community reviews

Loading reviews…