dbcve.org
Powerchute Serial ShutdownApplication · Schneider Electric

CVE-2026-2399

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 1.5 or later.
See remediation →
63/100
Remediation priority · Elevated
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
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability exists that could cause critical files overwritten with text data when a Web Admin user alters the POST /REST/upssleep request payload.

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

A path traversal vulnerability (CWE-22) in the /REST/uppsleep endpoint allows authenticated Web Admin users to manipulate POST request payloads and overwrite critical system files with arbitrary text data. The vulnerability stems from insufficient input validation on file path parameters in the uppsleep request handler.

MitigationImplement strict input validation and path sanitization on all file path parameters in the /REST/uppsleep endpoint, using allowlists and canonicalization to prevent directory traversal sequences. Restrict file write operations to designated safe directories.

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
Powerchute Serial ShutdownApplication
Affected:< 1.5

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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/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 Powerchute Serial Shutdown installation
    Locate the Powerchute Serial Shutdown software installation directory or check system for installed programs named 'Powerchute Serial Shutdown' or 'Powerchute'
    Affected if The software is installed on the system
  2. Determine installed version
    Access the software's About section, check the installed program version through Windows Programs and Features, or locate version info in the installation directory
    Affected if The installed version is lower than 1.5 (e.g., 1.4.x, 1.0.x, etc.)
  3. Verify Web Admin interface status
    Check if the Web Admin interface is enabled in the Powerchute configuration settings or service status
    Affected if Web Admin interface is enabled and accessible
  4. Confirm REST API endpoint exposure
    Check if the /REST/uppsleep endpoint is accessible by attempting to reach it (e.g., https://localhost:PORT/REST/uppsleep or checking configuration for REST API enablement)
    Affected if The REST API and /REST/uppsleep endpoint are exposed
  5. Review access control for authenticated users
    Examine user accounts configured in Powerchute to identify any accounts with Web Admin privileges
    Affected if There are Web Admin user accounts configured in the system

You are affected if Powerchute Serial Shutdown is installed with a version lower than 1.5 AND the Web Admin interface with REST API access is enabled and accessible to authenticated users.

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

Implement strict input validation and path sanitization on all file path parameters in the /REST/uppsleep endpoint, using allowlists and canonicalization to prevent directory traversal sequences. Restrict file write operations to designated safe directories.

Recommended fix Moderate confidence

Powerchute Serial Shutdown version 1.5

  1. Identify the current installed version of Powerchute Serial Shutdown
  2. Download Powerchute Serial Shutdown version 1.5 or later from the official Schneider Electric download source (download.schneider-electric.com)
  3. Follow Schneider Electric's standard upgrade procedure for Powerchute Serial Shutdown to apply the update
  4. Verify the installation was successful and the new version is running
  5. Test that the Web Admin functionality for the /REST/uppsleep endpoint is working as expected

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

Fix this in Powerchute Serial Shutdown Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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