dbcve.org
Powerchute Serial ShutdownApplication · Schneider Electric

CVE-2026-2401

MEDIUM · 5.0 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 1.5 or later.
See remediation →
50/100
Remediation priority · Moderate

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-532 Insertion of Sensitive Information into Log File vulnerability exists that could cause confidential information to be exposed when a Web Admin user executes a malicious file provided by an attacker.

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 CWE-532 log injection vulnerability where a Web Admin user executing a malicious file causes confidential information to be written to log files, exposing sensitive data through improperly secured or sanitized logs.

MitigationImplement input validation on files before execution, sanitize or redact sensitive data before logging, restrict log file access permissions, and implement log rotation with secure storage.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Powerchute Serial Shutdown is installed
    Locate the Schneider Electric Powerchute Serial Shutdown installation on the system using standard software inventory tools or by searching for the application in the system program directories.
    Affected if The software is not present on the system, the vulnerability does not apply.
  2. Determine the installed version
    Use the application's built-in version information feature, check the About dialog, or inspect the executable file properties to identify the exact version number.
    Affected if The installed version is less than 1.5, the system may be affected.
  3. Confirm Web Admin interface is enabled
    Check if the web-based administrative interface is accessible and active by attempting to reach the management portal or reviewing the service configuration.
    Affected if The Web Admin interface is disabled or not accessible, the attack surface is reduced.
  4. Check file execution capabilities
    Review the Web Admin configuration to determine if file upload or file execution features are available to administrative users.
    Affected if File execution/upload features are enabled for Web Admin users, the vulnerability can be exploited.
  5. Inspect log file permissions and locations
    Locate the log directories used by Powerchute Serial Shutdown and verify who has read access to these files.
    Affected if Log files are accessible to non-administrative users, sensitive data exposure is possible if exploitation occurs.

The environment is affected if Powerchute Serial Shutdown is installed with version less than 1.5 and the Web Admin interface with file execution capabilities is enabled.

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 input validation on files before execution, sanitize or redact sensitive data before logging, restrict log file access permissions, and implement log rotation with secure storage.

Recommended fix Moderate confidence

Powerchute Serial Shutdown version 1.5

  1. Identify the current installed version of Powerchute Serial Shutdown on the system
  2. Navigate to Schneider Electric's official download portal at download.schneider-electric.com
  3. Locate and download Powerchute Serial Shutdown version 1.5 or later
  4. Verify the downloaded installer matches the official Schneider Electric hash/signatures
  5. Execute the installer with appropriate administrative privileges
  6. Follow the on-screen prompts to complete the upgrade
  7. Restart any running Powerchute services if prompted
  8. Verify the new version is correctly installed and the vulnerability is resolved

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

Fix this in Powerchute Serial Shutdown Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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