dbcve.org
NplatformApplication · Nuvationenergy

CVE-2025-64124

HIGH · 8.8 CVSS v3.1 Published 2026-01-03
Fix available
A fix is available. Upgrade to after 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): 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 OS commands through unsanitized input fields, potentially achieving full system compromise. The vulnerability affects versions prior to 2.5.1 and is exploitable over the network with low attack complexity, requiring no privileges or user interaction.

MitigationUpgrade Multi-Stack Controller firmware to version 2.5.1 or later to remediate. If immediate patching is not possible, implement network segmentation and restrict administrative access as compensating controls.

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.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 Nuvation Energy Nplatform installation
    Locate the Nuvation Energy Multi-Stack Controller or Nplatform software in your environment. Check system inventory, device listings, or network scans for the product named 'Nuvationenergy Nplatform' or 'Nuvation Energy MSC'.
    Affected if The product is present in your environment.
  2. Determine installed firmware version
    Access the device management interface or system settings to retrieve the firmware/software version. Compare the installed version to the affected range: any version <= 2.5.1 is vulnerable.
    Affected if Installed version is 2.5.1 or earlier.
  3. Verify network accessibility of management interface
    Check if the MSC web-based management interface or command input endpoints are exposed to the network. Use network scanning to identify open ports or services associated with the Nplatform.
    Affected if The management interface is reachable over the network from untrusted segments.
  4. Check for unauthenticated input fields
    Inspect the web interface or API endpoints for input fields that accept user data. Look for parameters that may be processed by the underlying OS, such as configuration fields, diagnostic inputs, or system command interfaces.
    Affected if Unsanitized input fields are accessible without authentication or after valid authentication.

You are affected if Nuvation Energy Nplatform (Multi-Stack Controller) version 2.5.1 or earlier is installed and its management interface with command injection-vulnerable input fields 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 a release after 2.5.1
Interim mitigation

Upgrade Multi-Stack Controller firmware to version 2.5.1 or later to remediate. If immediate patching is not possible, implement network segmentation and restrict administrative access as compensating controls.

Recommended fix High confidence

Nplatform 2.5.1 or later

  1. 1. Identify the current installed version of Nuvation Energy Multi-Stack Controller (MSC) / Nplatform
  2. 2. Confirm the version is before 2.5.1 (vulnerable)
  3. 3. Obtain the Nuvation Energy 2.5.1 release from official Nuvation Energy channels or your vendor
  4. 4. Follow Nuvation Energy's official upgrade procedure for MSC devices
  5. 5. After upgrade, verify the new version is 2.5.1 or later
  6. 6. Test that the MSC functionality operates normally post-upgrade
Caveat Review Nuvation Energy release notes for 2.5.1 to check for any functional changes that may affect your deployment

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

Fix this in Nplatform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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