dbcve.org
Intelligent Power ProtectorApplication · Eaton

CVE-2026-22618

HIGH · 7.1 CVSS v3.1 Published 2026-04-16
Fix available
A fix is available. Upgrade to 2.00 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
A security misconfiguration was identified in Eaton Intelligent Power Protector (IPP), where an HTTP response header was set with an insecure attribute, potentially exposing users to web‑based attacks. This security issue has been fixed in the latest version of Eaton IPP software which is available on the Eaton download centre.

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

Eaton Intelligent Power Protector (IPP) has a security misconfiguration where an HTTP response header is set with an insecure attribute. This could allow web-based attacks such as cross-site scripting, session hijacking, or clickjacking depending on the specific header affected. The vulnerability is in the web component of the IPP software.

MitigationUpdate Eaton Intelligent Power Protector to the latest version available from the Eaton download centre to ensure the HTTP response header is configured with secure attributes.

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
Intelligent Power ProtectorApplication
Affected:< 2.00

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/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. Identify installed Eaton Intelligent Power Protector version
    Access the IPP web interface and navigate to Help > About, or check the software installation directory for version information. The exact location varies by installation method.
    Affected if The displayed version number is below 2.00 (for example, 1.xx or any version < 2.00)
  2. Capture HTTP response headers from the IPP web interface
    Use browser developer tools (Network tab), curl -I <ipp_web_url>, or an HTTP proxy to inspect the response headers returned by the IPP web server.
    Affected if Security-related headers such as X-Frame-Options, X-Content-Type-Options, Strict-Transport-Security, or Content-Security-Policy are missing, or existing headers use insecure values (e.g., X-Frame-Options: ALLOWALL)
  3. Verify the web component is enabled and accessible
    Confirm the IPP web interface is running by accessing its URL (typically https://localhost:4679 or similar). Check if login page or admin console responds.
    Affected if The web component is accessible and returns HTTP responses with missing or insecure security headers

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.00 or later
Fixed in 2.00
Interim mitigation

Update Eaton Intelligent Power Protector to the latest version available from the Eaton download centre to ensure the HTTP response header is configured with secure attributes.

Recommended fix Moderate confidence

2.00 or later (latest available version from Eaton download centre)

  1. 1. Identify the current version of Eaton Intelligent Power Protector installed in your environment.
  2. 2. Navigate to the official Eaton download centre (www.eaton.com) and locate the Intelligent Power Protector software downloads.
  3. 3. Download the latest available version of Eaton Intelligent Power Protector (version 2.00 or later).
  4. 4. Before upgrading, backup the current configuration and any relevant data according to Eaton's documentation.
  5. 5. Stop the Intelligent Power Protector service if it is running.
  6. 6. Install the downloaded latest version following Eaton's standard upgrade procedures.
  7. 7. After installation, restart the Intelligent Power Protector service.
  8. 8. Verify the installation was successful and confirm the HTTP response headers now use secure attributes.
Caveat Review Eaton's release notes for the latest version to check for any configuration or feature changes that may affect your deployment

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

Fix this in Intelligent Power Protector Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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