CVE-2025-36589
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 · uneditedDell Unisphere for PowerMax, version(s) 9.2.4.x, contain(s) an Improper Restriction of XML External Entity Reference vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to unauthorized access to data and resources outside of the intended sphere of control.
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 confidenceDell Unisphere for PowerMax version 9.2.4.x contains an XXE (XML External Entity) vulnerability where the XML parser improperly processes external entity references. A low-privileged remote attacker can exploit this to access data and resources outside the intended control sphere, potentially reading local files or performing SSRF attacks.
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= 9.2.4.18>= 9.2.4.17, < 9.2.4.19CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Unisphere for PowerMax versionLog into the Unisphere web interface and navigate to Help > About, or check the version via the management CLI if available. Record the exact version number displayed.Affected if Version is 9.2.4.18 (for standalone) or falls between 9.2.4.17 and 9.2.4.19 inclusive (for Virtual Appliance)
-
Confirm product variantDetermine whether the installation is Dell Unisphere for PowerMax (standalone) or Dell Unisphere for PowerMax Virtual Appliance. This distinction matters because the affected version ranges differ between the two products.Affected if Running the Virtual Appliance variant with version 9.2.4.17, 9.2.4.18, or any 9.2.4.x version prior to 9.2.4.19
-
Verify low-privileged user access to Unisphere interfaceCheck if any user accounts with read-only or standard (non-administrator) roles have active access to the Unisphere web interface. Review user role assignments in the Unisphere user management section.Affected if Low-privileged users have network access to the Unisphere interface; the vulnerability is exploitable by these users
-
Inspect XML input acceptance pointsIdentify any API endpoints, import functions, or configuration upload features within Unisphere that accept XML data. Common areas include: configuration backup/restore, import utilities, or diagnostic data submission.Affected if The Unisphere interface exposes any functionality that processes user-supplied XML without explicit disablement of external entity processing
-
Review access logs for anomalous XML payloadsExamine Unisphere access logs and audit trails for requests containing XML with entity references (such as <!ENTITY>, SYSTEM, PUBLIC). Look for patterns like file:// or http:// schemes in XML input.
Your environment is affected if running Dell Unisphere for PowerMax version 9.2.4.18 or Virtual Appliance versions 9.2.4.17 through 9.2.4.18, and low-privileged users can access the Unisphere interface where XML input is processed.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.2.4.19
Upgrade to a patched version of Dell Unisphere for PowerMax, or disable external entity processing in XML parsers if a patch is unavailable. Restrict low-privileged user access to the Unisphere interface until remediated.
Unisphere For PowerMax/PowerMax Virtual Appliance version 9.2.4.19 or later
- Upgrade Unisphere For PowerMax version 9.2.4.18 to version 9.2.4.19 or later
- Upgrade Unisphere For PowerMax Virtual Appliance from versions 9.2.4.17 or 9.2.4.18 to version 9.2.4.19 or later
- After upgrading, verify the vulnerability is resolved by reviewing the release notes for the new version
- Consult Dell support or documentation for specific upgrade procedures for your deployment type
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36589 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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