Skip to main content
VulnerabilityPublished

CVE-2026-59233: 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.2.1 soon.

Data as of 8 Nov 2026, 23:24 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 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 8 Nov 2026.

What to do

Upgrade Roskus Prospero Flow CRM to 5.2.1.

Affected software

ProductAffectedFixed in
RoskusProspero Flow CRMAffected
  • <5.2.1
Fixed in
  • 5.2.1
GitHubProspero Flow CRMpkg:github/Prospero Flow CRMOther threatsAffected
  • <5.2.1
Fixed in
  • 5.2.1

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 permission management functionality to trusted administrators only and monitor for suspicious permission changes.

Description

CVE-2026-59233 is a high-severity authorization bypass vulnerability in Roskus Prospero Flow CRM versions prior to 5.2.1. The flaw exists in the permission management component, where the permission save endpoint does not perform authorization checks. This allows any authenticated user to grant any role, including their own, full application permissions by sending a crafted POST request.

References

Community reviews

Loading reviews…