CVE-2025-36595
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 vApp, version(s) 9.2.4.x, contain(s) an Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to Code 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 · moderate confidenceDell Unisphere for PowerMax vApp version 9.2.4.x contains a Static Code Injection vulnerability where user-controlled input is embedded into statically saved code (likely HTML, JavaScript, or configuration files) without proper sanitization. An authenticated high-privileged attacker with remote access can inject malicious code that gets executed in the context of the application, potentially leading to arbitrary code execution.
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.0, < 9.2.4.11>= 9.2.4.0, < 9.2.4.17CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed product versionAccess the virtual appliance management interface or use system commands to retrieve the version information (typically found in about/settings pages or via CLI 'show version' or similar command)Affected if The version is >= 9.2.4.0 and < 9.2.4.11 for Dell Solutions Enabler Virtual Appliance, or >= 9.2.4.0 and < 9.2.4.17 for Dell Unisphere For Powermax Virtual Appliance
-
Confirm administrative web interface is enabledVerify the Unisphere or Solutions Enabler web management console is accessible via browser on the configured port (typically 443 or 8443)Affected if The web interface is exposed and accessible to the network where an attacker could reach it
-
Verify administrative account configurationCheck if administrative accounts with remote access privileges exist in the system (via user management section in the appliance console or command-line user enumeration)Affected if Administrative users with remote access capabilities are present in the system
-
Inspect user-modifiable content areasReview any fields or interfaces where user-supplied data can be saved and persists as static content (such as system descriptions, labels, custom scripts, or configuration text fields accessible via the admin interface)Affected if User-supplied input can be saved and rendered as static code without sanitization visible in the application
You are affected if your installed version falls within the vulnerable ranges AND the web administrative interface is accessible with valid high-privileged accounts present.
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.119.2.4.17
Apply vendor-supplied patches when available; until then, restrict administrative access to trusted users only, implement strict input validation on all user-supplied data before embedding in static content, and monitor for suspicious administrative activity.
Solutions Enabler: 9.2.4.11 or later; Unisphere For Powermax: 9.2.4.17 or later
- 1. Identify which Dell virtual appliance is in use: Solutions Enabler Virtual Appliance or Unisphere For Powermax Virtual Appliance
- 2. For Solutions Enabler Virtual Appliance: Upgrade to version 9.2.4.11 or later
- 3. For Unisphere For Powermax Virtual Appliance: Upgrade to version 9.2.4.17 or later
- 4. Obtain the upgrade from Dell's official support portal at www.dell.com
- 5. Follow Dell's standard upgrade procedure for the respective virtual appliance
- 6. After upgrade, verify the new version is running and confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36595 — 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-36595 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