dbcve.org
DiskpulseApplication · Flexense

CVE-2025-59896

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Sync Breeze Enterprise Server v10.4.18 and Disk Pulse Enterprise v10.4.18 contain a persistent authenticated Cross-Site Scripting (XSS) vulnerability. An attacker could send malicious content to an authenticated user and steal information from their session due to insufficient validation of user input in '/add_command?sid=', affecting the 'command_name' parameter.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Persistent authenticated XSS vulnerability in Sync Breeze Enterprise Server v10.4.18 and Disk Pulse Enterprise v10.4.18 allows authenticated attackers to inject malicious scripts via the 'command_name' parameter in the '/add_command?sid=' endpoint. The injected payload persists and can be executed in other users' sessions, enabling session hijacking and information theft.

MitigationImplement strict input validation and context-aware output encoding for the 'command_name' parameter; add Content Security Policy (CSP) headers to mitigate XSS execution; consider implementing CSRF tokens for state-changing operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DiskpulseApplication
Affected:= 10.4.18
SyncbreezeApplication
Affected:= 10.4.18

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product and version
    Check the installed version of Flexense Diskpulse or Syncbreeze Enterprise by reviewing installed software details, checking the application's About/Help section, or querying the service banner. For Disk Pulse, check the DiskPulse.exe properties or service info. For Sync Breeze, check SyncBreeze.exe properties or service info.
    Affected if Version is exactly 10.4.18 for either Diskpulse or Syncbreeze Enterprise
  2. Confirm enterprise edition is in use
    Verify the installed edition is the Enterprise version, as only Enterprise editions include the '/add_command' endpoint with command management features. Check the product name displayed in the application or service description.
    Affected if The installed product is Disk Pulse Enterprise or Sync Breeze Enterprise version 10.4.18 (not Standard or Professional editions)
  3. Verify the web interface is enabled
    Determine if the HTTP/HTTPS web management interface is enabled. Check Windows services for DiskPulse or SyncBreeze web service status, or review the application configuration for web server binding settings.
    Affected if The web management interface is enabled and accessible on the configured port (default varies by product)
  4. Confirm authentication is active but exploitable
    Review the web interface authentication configuration to confirm user accounts are configured. The vulnerability requires an authenticated session to access the '/add_command?sid=' endpoint, but the XSS persists across sessions.
    Affected if User authentication is configured for the web interface, allowing login to obtain a session ID (sid)
  5. Inspect web server logs for suspicious add_command activity
    Review HTTP access logs for the application (typically in the product's log directory) for entries involving POST or GET requests to '/add_command' with unusual command_name parameter values containing script tags or encoded characters.
    Affected if Log entries show requests to /add_command with potentially malicious command_name values that were successfully processed

You are affected if running Disk Pulse Enterprise or Sync Breeze Enterprise version 10.4.18 with the web interface enabled and authentication configured, allowing access to the vulnerable /add_command endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and context-aware output encoding for the 'command_name' parameter; add Content Security Policy (CSP) headers to mitigate XSS execution; consider implementing CSRF tokens for state-changing operations.

Fix this in Diskpulse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59896 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59896 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data