dbcve.org
DiskpulseApplication · Flexense

CVE-2025-59899

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  '/server_options?sid=', affecting the 'tasks_logs_dir', 'errors_logs_dir', 'error_notifications_address', 'status_notifications_address', and 'status_reports_address' parameters.

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 · high confidence

Persistent authenticated XSS in Sync Breeze Enterprise Server and Disk Pulse Enterprise v10.4.18. The application fails to sanitize user input in the /server_options?sid= endpoint, specifically in the tasks_logs_dir, errors_logs_dir, error_notifications_address, status_notifications_address, and status_reports_address parameters, allowing stored malicious JavaScript to execute in authenticated users' browsers.

MitigationImplement strict input validation and output encoding for all user-supplied parameters in the server_options functionality. Since this is a persistent XSS, the fix must prevent malicious scripts from being stored and also ensure proper escaping when the data is rendered.

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 the installed version of Disk Pulse or Sync Breeze
    Locate the application in the system and check its version property. For Disk Pulse Enterprise, look for 'Diskpulse' in installed programs. For Sync Breeze Enterprise, look for 'Syncbreeze'. Confirm the exact version is 10.4.18.
    Affected if The installed version is exactly 10.4.18 for either Flexense Diskpulse or Flexense Syncbreeze.
  2. Verify the web server component is running
    Check if the Disk Pulse or Sync Breeze web service is listening on its configured port (typically HTTP port 80 or 443, or a custom port). Use netstat or similar tool to enumerate active listening ports associated with the application.
    Affected if The web interface is accessible and the application is running.
  3. Confirm authentication is configured for the web interface
    Access the login page of the web interface (typically http://hostname:port or http://hostname). Verify that a session ID parameter (sid) is required to access protected functionality.
    Affected if The application requires authentication and issues session IDs.
  4. Locate the vulnerable server_options endpoint
    With valid credentials, navigate to or request the /server_options endpoint with a valid session ID (sid) parameter. Identify the form fields: tasks_logs_dir, errors_logs_dir, error_notifications_address, status_notifications_address, and status_reports_address.
    Affected if The /server_options?sid= endpoint is accessible and contains the five vulnerable parameters.
  5. Test for stored XSS in the affected parameters
    After authenticating, submit benign HTML/JavaScript payloads (such as <script>alert(1)</script>) in each of the five parameters through the server_options form. Save the configuration and then reload the page or view the saved values to observe if the payload executes without encoding.
    Affected if The submitted payload is rendered unescaped in the browser when the saved settings are displayed, indicating the XSS vulnerability is present.

A user is affected if they are running Disk Pulse Enterprise or Sync Breeze Enterprise version 10.4.18, have the web interface enabled with authentication, and can access the /server_options endpoint where user-supplied input in the five specified parameters is stored and displayed without proper sanitization.

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 output encoding for all user-supplied parameters in the server_options functionality. Since this is a persistent XSS, the fix must prevent malicious scripts from being stored and also ensure proper escaping when the data is rendered.

Fix this in Diskpulse Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59899 — 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-59899 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