dbcve.org
Unisphere For PowermaxApplication · Dell

CVE-2025-36588

HIGH · 8.8 CVSS v3.1 Published 2026-01-22
Fix available
A fix is available. Upgrade to 9.2.4.19 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Dell Unisphere for PowerMax, version(s) 10.2.0.x, contain(s) an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Command execution.

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

Dell Unisphere for PowerMax version 10.2.0.x contains a SQL injection vulnerability where improper neutralization of special elements in SQL commands allows a low-privileged remote attacker to execute commands. The vulnerability is exploitable with remote network access and achieves high severity (CVSS 8.8) due to the potential for complete command execution on the underlying system.

MitigationApply vendor-supplied patches for Dell Unisphere for PowerMax 10.2.0.x immediately. If no patch is available, restrict network access to the Unisphere management interface and implement web application firewall rules to detect and block SQL injection payloads until a fix is released.

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
Unisphere For PowermaxApplication
Affected:< 9.2.4.19
Unisphere For Powermax Virtual ApplianceApplication
Affected:< 9.2.4.19

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Dell Unisphere for PowerMax installation
    Locate the Unisphere installation directory or check the web application running on the management port (typically 8443 or 443). Access the web UI and look for the version information, usually found in the About or Help section of the interface.
    Affected if Dell Unisphere for PowerMax or Unisphere for PowerMax Virtual Appliance is present and accessible on the network.
  2. Verify installed version against affected ranges
    In the Unisphere web interface, navigate to the About or System Information page to find the exact version number. Alternatively, check the version via CLI if available. Compare the version to 9.2.4.19.
    Affected if The installed version is lower than 9.2.4.19 (for example, 9.2.4.0 through 9.2.4.18, or version 10.2.0.x as mentioned in the summary).
  3. Confirm network accessibility of Unisphere management interface
    Determine if the Unisphere web interface is exposed to the network. Check firewall rules, load balancer configurations, or network segmentation settings to see if the management port is reachable from outside the trusted network.
    Affected if The Unisphere management interface is reachable from untrusted networks or the internet, enabling remote attackers to reach the vulnerable SQL injection endpoint.
  4. Identify SQL injection attack surface
    Review the Unisphere web application for user input fields that interact with backend databases. Common areas include search functions, filtering options, login parameters, or any endpoint accepting user-supplied data that gets passed to SQL queries.
    Affected if Any user-accessible input field or API endpoint accepts parameters that are not properly sanitized before being used in SQL queries.

The environment is affected if Dell Unisphere for PowerMax or its Virtual Appliance version is below 9.2.4.19 and the management interface is network-accessible to potential attackers.

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.

dbcve · scoped
Upgrade available Upgrade to 9.2.4.19 or later
Fixed in 9.2.4.19
Interim mitigation

Apply vendor-supplied patches for Dell Unisphere for PowerMax 10.2.0.x immediately. If no patch is available, restrict network access to the Unisphere management interface and implement web application firewall rules to detect and block SQL injection payloads until a fix is released.

Recommended fix High confidence

Unisphere For Powermax 9.2.4.19 (or later) / Unisphere For Powermax Virtual Appliance 9.2.4.19 (or later)

  1. 1. Identify current Unisphere for PowerMax version by navigating to the Unisphere UI and checking the About section, or via CLI using 'symcfg -version'
  2. 2. Schedule a maintenance window for the upgrade procedure
  3. 3. Back up current Unisphere configuration and any custom settings
  4. 4. Download Unisphere for PowerMax version 9.2.4.19 or later from Dell Support (www.dell.com/support)
  5. 5. For physical Appliance: Use the Unisphere upgrade utility or follow Dell's documented upgrade procedure for the specific model
  6. 6. For Virtual Appliance: Follow the VMware-based upgrade procedure documented in the Unisphere Virtual Appliance deployment guide
  7. 7. After upgrade, verify the new version number matches 9.2.4.19 or higher in the About section
  8. 8. Validate that core services (Storage provisioning, masking, replication) function correctly post-upgrade
Caveat Review Dell Unisphere release notes for 9.2.4.x for any configuration changes or migration requirements; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unisphere For Powermax Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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