Skip to main content
VulnerabilityPublished

CVE-2025-59891: 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, 17:16 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 26 Oct 2026.

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 include restricting access to the Sync Breeze Enterprise Server and Disk Pulse Enterprise management interfaces to trusted networks and IP addresses, minimizing exposure to potential attackers.
  2. Implement web application firewalls (WAFs) with rules designed to detect and block suspicious POST requests to the affected endpoints, especially those attempting to modify user credentials or create accounts.
  3. Enforce multi-factor authentication (MFA) for all users accessing the affected applications to reduce the risk of account compromise even if CSRF attacks succeed.
  4. Monitor logs for unusual activities such as unexpected password changes or new user creations, and establish alerting mechanisms for such events.
  5. Until an official patch is released, consider disabling or restricting the vulnerable endpoints if feasible, or applying custom CSRF token validation via reverse proxies or application-layer controls.
  6. Educate users about the risks of CSRF and encourage best practices such as logging out after sessions and avoiding untrusted websites while logged in.
  7. Plan for rapid deployment of vendor patches once available and verify their effectiveness through security testing.
  8. Conduct regular security assessments and penetration tests focusing on web application vulnerabilities including CSRF to proactively identify and remediate similar issues.

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 change a user's password or create users via '/setup_login?sid=', affecting the 'username', 'password', and 'cpassword' parameters.

References

Community reviews

Loading reviews…