CVE-2021-23276
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 · uneditedEaton Intelligent Power Manager (IPM) prior to 1.69 is vulnerable to authenticated SQL injection. A malicious user can send a specially crafted packet to exploit the vulnerability. Successful exploitation of this vulnerability can allow attackers to add users in the data base.
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 · high confidenceEaton Intelligent Power Manager (IPM) versions prior to 1.69 contain an authenticated SQL injection vulnerability. An authenticated attacker can send specially crafted packets to inject malicious SQL queries, enabling unauthorized database manipulation including the creation of new user accounts.
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< 1.69< 1.69< 1.68CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Eaton softwareReview installed programs or software inventory on the system for Eaton Intelligent Power Manager, Eaton Intelligent Power Manager Virtual Appliance, or Eaton Intelligent Power ProtectorAffected if Any of these products are installed and the version is below the fixed release
-
Check Eaton IPM versionLocate the installed version of Eaton Intelligent Power Manager through the application, itsAbout dialog, Windows Programs and Features, or installation directory metadataAffected if Version is lower than 1.69
-
Check Eaton IPM Virtual Appliance versionAccess the virtual appliance system information, web interface, or VM inventory to determine the IPM Virtual Appliance versionAffected if Version is lower than 1.69
-
Check Eaton IP Protector versionLocate the installed version of Eaton Intelligent Power Protector through the application, Windows Programs and Features, or installation directory metadataAffected if Version is lower than 1.68
You are affected if any Eaton Intelligent Power Manager, IPM Virtual Appliance, or IP Protector instance with a version below 1.69 (or below 1.68 for IP Protector) is installed on your network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.681.69
Upgrade Eaton Intelligent Power Manager to version 1.69 or later to remediate this vulnerability. If immediate patching is not possible, implement network segmentation and restrict administrative access to minimize the attack surface.
Intelligent Power Manager: 1.69+ | Intelligent Power Manager Virtual Appliance: 1.69+ | Intelligent Power Protector: 1.68+
- Identify all deployed instances of Eaton Intelligent Power Manager, Intelligent Power Manager Virtual Appliance, and Intelligent Power Protector in your environment
- For Intelligent Power Manager, upgrade to version 1.69 or later
- For Intelligent Power Manager Virtual Appliance, upgrade to version 1.69 or later
- For Intelligent Power Protector, upgrade to version 1.68 or later
- After upgrading, verify that the SQL injection vulnerability is no longer present by reviewing release notes or consulting Eaton support
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23276 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-23276 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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