dbcve.org
NplatformApplication · Nuvationenergy

CVE-2025-64120

HIGH · 8.8 CVSS v3.1 Published 2026-01-02
Fix available
A fix is available. Upgrade to 2.5.1 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
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Nuvation Energy Multi-Stack Controller (MSC) allows OS Command Injection.This issue affects Multi-Stack Controller (MSC): from 2.3.8 before 2.5.1.

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 confidence

OS Command Injection vulnerability in Nuvation Energy Multi-Stack Controller (MSC) allows remote attackers to execute arbitrary operating system commands due to improper neutralization of special elements in user-supplied input. The vulnerability affects versions from 2.3.8 before 2.5.1, and successful exploitation could allow complete compromise of the controller.

MitigationUpgrade Multi-Stack Controller (MSC) to version 2.5.1 or later to remediate this vulnerability. If immediate patching is not possible, implement network segmentation and restrict access to the MSC management interfaces.

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
NplatformApplication
Affected:>= 2.3.8, < 2.5.1

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 Nplatform version
    Locate the installed version of Nuvation Energy Nplatform or Multi-Stack Controller (MSC) through its web management interface, system information page, or firmware metadata. This is typically found under About, System Info, or Diagnostics sections of the MSC web UI.
    Affected if The installed version is 2.3.8, 2.4.x, or any version >= 2.3.8 but lower than 2.5.1
  2. Verify MSC web interface accessibility
    Determine if the MSC web management interface is reachable over the network. Check if port 80/443 or the MSC HTTP service is exposed to network segments that are not strictly controlled.
    Affected if The MSC management interface is accessible from network segments that include untrusted or attacker-controlled systems
  3. Check for input handling exposure
    Identify which MSC functions accept user-supplied input that could be passed to operating system commands. Common areas include configuration parameters, diagnostics tools, or troubleshooting features that invoke system utilities.
    Affected if User-controllable input fields exist in the MSC interface that could be processed by system command interpreters
  4. Assess network segmentation
    Review network topology to determine whether the MSC is isolated from untrusted networks or if it shares network segments with less-trusted systems.
    Affected if The MSC management interface is on a network segment accessible from broader corporate or external networks without proper firewall or access control boundaries

You are affected if your Nplatform/MSC version is 2.3.8 or any version from 2.4.0 through 2.5.0 and the MSC management interface is network-accessible.

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 2.5.1 or later
Fixed in 2.5.1
Interim mitigation

Upgrade Multi-Stack Controller (MSC) to version 2.5.1 or later to remediate this vulnerability. If immediate patching is not possible, implement network segmentation and restrict access to the MSC management interfaces.

Recommended fix Moderate confidence

Nplatform 2.5.1 or later

  1. Identify current Nplatform/MSC version by checking the system interface or running: version check command
  2. Backup current configuration and data before upgrading
  3. Download Nplatform version 2.5.1 or later from the vendor (Nuvation Energy)
  4. Apply the upgrade following the vendor's standard upgrade procedure, typically: systemctl stop ms-controller, run upgrade installer, systemctl start ms-controller
  5. Verify the upgrade was successful by checking the version number and ensuring all services are running
  6. Test critical functionality to confirm the OS command injection vulnerability is resolved
Caveat Review vendor release notes for 2.5.1 for any configuration or feature changes that may require adjustment

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

Fix this in Nplatform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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