Skip to main content
VulnerabilityPublished

CVE-2026-59232: Roskus Prospero Flow CRM · Cross-site Scripting

Affects Roskus Prospero Flow CRMSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 5.3.7 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
5.3Medium
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.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jul 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 30 Oct 2026.

What to do

Upgrade Roskus Prospero Flow CRM to 5.3.7.

Affected software

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

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 create and update lead permissions to trusted users only and consider input validation or sanitization on the lead name field to prevent injection of malicious markup.

Description

Cross-site Scripting in the lead index view in Roskus Prospero Flow CRM before 5.3.7 allows authenticated users holding the create or update lead permission to execute arbitrary JavaScript in the application origin via HTML markup stored in the lead name field, which the view renders through Blade's unescaped output directive and inside a JavaScript string literal in an onclick attribute.

References

Community reviews

Loading reviews…