CVE-2025-59893: Flexense Sync Breeze Enterprise Server · Cross-Site Request Forgery (CSRF)
Affects Flexense Sync Breeze Enterprise ServerSource CVE Database V5
Not known to be exploited · CVSS 8.5 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FlexenseSync Breeze Enterprise Server | Affected
| Fixed in– |
| FlexenseDisk Pulse Enterprise | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation should focus on restricting access to the Sync Breeze Enterprise Server and Disk Pulse Enterprise interfaces to trusted users only, employing network segmentation and firewall rules to limit exposure. 2. Implement web application firewalls (WAF) with custom rules to detect and block suspicious POST requests targeting the '/rename_command?sid=' endpoint or anomalous command renaming activities. 3. Enforce strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise. 4. Monitor logs and audit trails for unusual command renaming actions or unexpected user behaviors indicative of CSRF exploitation attempts. 5. Engage with Flexense for official patches or updates addressing the CSRF vulnerability and apply them promptly once available. 6. Educate users about the risks of CSRF and encourage cautious behavior when interacting with links or requests while authenticated. 7. Where possible, implement additional CSRF protections at the application or proxy level, such as validating the Origin or Referer headers. 8. Regularly review and update security policies to incorporate lessons learned from this vulnerability and enhance overall application security posture.
Description
Cross-Site request forgery (CSRF) vulnerability in Sync Breeze Enterprise Server v10.4.18 and Disk Pulse Enterprise v10.4.18. An authenticated user could cause another user to perform unwanted actions within the application they are logged into. This vulnerability is possible due to the lack of proper CSRF token implementation. Among other things, it is possible, using a POST request to rename commands via '/rename_command?sid=', affecting the 'command_name' parameter.