dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-59901

HIGH · 8.5 CVSS v4.0 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 →
89/100
Remediation priority · High
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
Disk Pulse Enterprise v10.4.18 has an authenticated reflected XSS vulnerability in the '/monitor_directory?sid=' endpoint, caused by insufficient validation of the 'monitor_directory' parameter sent by POST. An attacker could exploit this weakness to send malicious content to an authenticated user and steal information from their session.

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

Disk Pulse Enterprise v10.4.18 contains an authenticated reflected XSS vulnerability in the /monitor_directory?sid= endpoint. The 'monitor_directory' POST parameter is not properly validated or sanitized, allowing attackers to inject malicious script content that executes within an authenticated user's browser context.

MitigationImplement strict input validation and output encoding for the 'monitor_directory' parameter, and deploy Content Security Policy headers to mitigate XSS attacks.

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

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
Authentication
X
User interaction
A
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm Disk Pulse Enterprise is installed
    Locate the Disk Pulse Enterprise installation and identify the exact version number. Check the application GUI about dialog, installation directory for version info, or query the application service if available.
    Affected if The installed version is Disk Pulse Enterprise 10.4.18 or an unpatched version within the 10.4.x range where the vulnerability exists.
  2. Verify the /monitor_directory endpoint exists
    Check if the web interface or API for Disk Pulse Enterprise exposes the '/monitor_directory' endpoint. This is typically accessible via the administrative web console.
    Affected if The '/monitor_directory' endpoint is present and accessible in the application.
  3. Confirm authentication is enabled
    Review the application's security settings to verify that user authentication is required for accessing the '/monitor_directory' endpoint. Check if anonymous access is permitted.
    Affected if Authentication is required but the application does not properly sanitize the 'monitor_directory' POST parameter before reflecting it in the response.
  4. Inspect the application's response handling
    If you have access to the application logs or can perform a controlled test, submit a benign test string (such as a simple alphanumeric value) to the 'monitor_directory' POST parameter and examine whether the value is reflected unsanitized in the response.
    Affected if The submitted 'monitor_directory' parameter value is reflected directly in the response without encoding or validation, indicating the XSS vulnerability is present.
  5. Review web server configuration
    Examine the web server or application configuration files for Disk Pulse Enterprise to determine if output encoding or input validation filters are applied to the '/monitor_directory' endpoint.
    Affected if No input validation or output encoding mechanisms are configured for the monitor_directory parameter.

The environment is affected if Disk Pulse Enterprise version 10.4.18 is running, the '/monitor_directory' endpoint is accessible, and the 'monitor_directory' POST parameter is reflected in responses without proper sanitization or encoding.

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 the 'monitor_directory' parameter, and deploy Content Security Policy headers to mitigate XSS attacks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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