CVE-2025-59892: 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, 06:26 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
To mitigate CVE-2025-59892, European organizations should: 1) Apply any available patches or updates from Flexense as soon as they are released. 2) If patches are not yet available, implement web application firewall (WAF) rules to detect and block suspicious POST requests to the '/delete_command' endpoint, especially those lacking valid CSRF tokens or originating from untrusted sources. 3) Enforce strict same-site cookie policies and validate the Origin and Referer headers on the server side to prevent cross-origin requests. 4) Educate users about phishing and social engineering risks to reduce the likelihood of clicking malicious links. 5) Conduct regular security audits and penetration testing focusing on CSRF and other web vulnerabilities. 6) Limit user privileges where possible to reduce the impact of compromised accounts. 7) Monitor logs for unusual deletion commands or patterns indicative of CSRF exploitation attempts. 8) Consider implementing multi-factor authentication to strengthen user authentication and reduce risk of account compromise. These steps go beyond generic advice by focusing on immediate compensating controls and user awareness until official patches are deployed.
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 delete commands individually via '/delete_command?sid=', using the 'cid' parameter.