dbcve.org
Powerchute Serial ShutdownApplication · Schneider Electric

CVE-2026-2404

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 1.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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-116 Improper Encoding or Escaping of Output vulnerability exists that could cause log injection and forged log when an attacker alters the POST /j_security check 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 CWE-116 Improper Encoding or Escaping of Output vulnerability in the POST /j_security check endpoint allows attackers to inject arbitrary content into logs by manipulating the request payload. The application fails to properly encode or escape output before writing to logs, enabling log injection and forged log entries.

MitigationImplement proper output encoding/escaping for all data written to logs, particularly authentication-related data from the j_security check endpoint. Use structured logging or log sanitization functions to prevent log injection.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Confirm Powerchute Serial Shutdown is installed
    Locate the Powerchute Serial Shutdown application on the system. Check installed programs on Windows or look for the application directory on the operating system where it was deployed.
    Affected if The application is not installed on the system.
  2. Identify the installed version
    Open Powerchute Serial Shutdown and navigate to Help > About, or check the application's version information in the Windows Add/Remove Programs panel, or inspect the version metadata in the installation directory.
    Affected if The installed version is any version prior to 1.5 (for example, 1.4.x, 1.3.x, or earlier).
  3. Verify the web interface is accessible
    Attempt to reach the Powerchute web interface by opening a browser and navigating to the default HTTPS port (typically port 6547) on the host where Powerchute is running, such as https://localhost:6547 or https://<device_ip>:6547.
    Affected if The web interface is not accessible or the service is not running.
  4. Confirm the j_security_check endpoint exists
    Send a POST request to the /j_security_check endpoint on the web interface using a tool like curl: curl -k -X POST https://<host>:6547/j_security_check -d "j_username=test&j_password=test"
    Affected if The endpoint responds (indicating it exists and is reachable).
  5. Check for log injection test response
    Send a POST request to /j_security_check with newline characters in the j_username parameter (for example, j_username=test%0aInjectedLogEntry) and examine the application logs for any unencoded output.
    Affected if Log files show the injected content without encoding or escaping of the newline characters.

The environment is affected if Powerchute Serial Shutdown version 1.5 or higher is NOT installed AND the web interface with the /j_security_check endpoint is 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 1.5 or later
Fixed in 1.5
Interim mitigation

Implement proper output encoding/escaping for all data written to logs, particularly authentication-related data from the j_security check endpoint. Use structured logging or log sanitization functions to prevent log injection.

Recommended fix Moderate confidence

Powerchute Serial Shutdown version 1.5

  1. 1. Identify all systems running Powerchute Serial Shutdown versions prior to 1.5
  2. 2. Download the Powerchute Serial Shutdown version 1.5 from the official Schneider Electric download portal (download.schneider-electric.com)
  3. 3. Review the Schneider Electric release notes and installation documentation for version 1.5
  4. 4. Create a backup of current configuration and data
  5. 5. Uninstall the current version of Powerchute Serial Shutdown
  6. 6. Install version 1.5 following the vendor's installation guide
  7. 7. Restore the configuration if needed
  8. 8. Verify the application is running correctly and test the /j_security check functionality

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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