CVE-2026-59239 Roskus CVE debrief

Who should care

Administrators and users of Roskus Prospero Flow CRM versions before 5.4.4 should be aware of this vulnerability and take immediate action to update their systems to prevent exploitation. This vulnerability affects operators who use the email module, platform administrators who manage user accounts, and security teams who monitor for suspicious activity.

Technical summary

The vulnerability is caused by the lack of sanitization and unescaped rendering of email bodies in Roskus Prospero Flow CRM. An authenticated low-privileged user can inject malicious JavaScript code into an email body, which is then executed in the browser of another user, including administrators, when they open the message. This can lead to session compromise and account takeover. The vulnerability affects Roskus Prospero Flow CRM before version 5.4.4.

Defensive priority

High

Recommended defensive actions

• Update Roskus Prospero Flow CRM to version 5.4.4 or later
• Implement additional security measures, such as input validation and output encoding
• Monitor for suspicious activity and implement incident response plans
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-07-27T18:16:57.300Z and has not been modified since then. The NVD entry is currently being processed. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The vulnerability is caused by the lack of sanitization and unescaped rendering of email bodies in Roskus Prospero Flow CRM.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.