Skip to main content
CVE-2025-59894VulnerabilityPublished

CVE-2025-59894: Flexense Sync Breeze Enterprise Server · Cross-Site Request Forgery (CSRF)

Affects Flexense Sync Breeze Enterprise ServerSource CVE Database V5

0

Not known to be exploited · CVSS 8.5 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
FlexenseSync Breeze Enterprise ServerAffected
  • =10.4.18
Fixed in–
FlexenseDisk Pulse EnterpriseAffected
  • =10.4.18
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 networks and users only, reducing exposure to potential CSRF attacks. 2. Implement web application firewall (WAF) rules to detect and block suspicious POST requests targeting the '/delete_all_commands' endpoint or other sensitive actions. 3. Educate users about phishing and social engineering tactics to reduce the likelihood of falling victim to malicious CSRF links or requests. 4. Monitor logs for unusual POST requests or command deletions that could indicate attempted exploitation. 5. Once available, apply vendor patches or updates that address the CSRF vulnerability and introduce proper CSRF token validation. 6. If patching is delayed, consider deploying reverse proxies or API gateways that enforce CSRF protections or require additional authentication factors for sensitive operations. 7. Enforce strict session management policies, including short session timeouts and re-authentication for critical actions, to limit the window of opportunity for attackers. 8. Conduct regular security assessments and penetration tests focusing on web application vulnerabilities, including CSRF, to identify and remediate weaknesses proactively.

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 all commands via '/delete_all_commands?sid='.

References

Community reviews

Loading reviews…