Skip to content
Web

CVE-2025-59893

8.5
High
EPSS 0.13%Patch availableJan 28, 2026

CSRF in Sync Breeze Enterprise Server 10.4.18 and Disk Pulse 10.4.18 enables actions via authenticated POST.

common questions

Is CVE-2025-59893 being exploited?

Not confirmed. CVE-2025-59893 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2025-59893?

CVE-2025-59893 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-59893?

Yes. A fix has been recorded for CVE-2025-59893. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-59893 affect?

CVE-2025-59893 affects Sync Breeze Enterprise Server v10.4.18, Disk Pulse Enterprise v10.4.18. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-59893?

Apply vendor patch; enable CSRF protection on all endpoints.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Sync Breeze Enterprise Server v10.4.18Disk Pulse Enterprise v10.4.18
impact

Authenticated user can trigger actions on behalf of another user (e.g., rename_command) via CSRF, risking unintended changes.

action required

Immediate action required

affected versions
Flexense Disk Pulse Enterprise
  • affectedv10.4.18
Flexense Sync Breeze Enterprise Server
  • affectedv10.4.18

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free