CVE-2021-22763
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 · uneditedA CWE-640: Weak Password Recovery Mechanism for Forgotten Password vulnerability exists in PowerLogic PM55xx, PowerLogic PM8ECC, PowerLogic EGX100 and PowerLogic EGX300 (see security notification for version infromation) that could allow an attacker administrator level access to a device.
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 confidenceCWE-640 vulnerability in PowerLogic PM55xx, PM8ECC, EGX100, and EGX300 devices allows attackers to exploit a weak password recovery mechanism for forgotten passwords, enabling unauthorized administrator-level access to the device.
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< 2.7.8< 10.7.3<= 2.5.4< 2.7.8all versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the PowerLogic device modelAccess the device web interface or console and locate the device model identifier (PM5560, PM5561, PM5562, PM5563, PM8ECC, EGX100, or EGX300) in the device information or status pageAffected if The device model is one of: PM5560, PM5561, PM5562, PM5563, PM8ECC, EGX100, or EGX300
-
Check the installed firmware versionNavigate to the device firmware or system information page in the web interface, or use the device console/CLI to retrieve the firmware version stringAffected if The firmware version is below the fixed version for your model (PM5560/PM5563: 2.7.8, PM5561: 10.7.3, PM5562: 2.5.4, or PM8ECC: any version)
-
Confirm network accessibility of password recovery interfaceVerify that the device management interface (HTTP/HTTPS web portal) is reachable from the network where password recovery would be attemptedAffected if The device management interface is exposed to network segments where unauthorized users could reach it
You are affected if your device model is in the affected list and the installed firmware version falls below the fixed version (or is any version for PM8ECC), combined with network accessibility of the management interface.
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 · scoped2.7.810.7.3
Apply vendor-supplied firmware updates addressing the weak password recovery mechanism; if unavailable, restrict network access to management interfaces and implement additional authentication controls.
Upgrade to firmware 2.7.8 (Pm5560/Pm5563), 10.7.3 (Pm5561), 2.5.5+ (Pm5562); contact Schneider for PM8ECC
- 1. Identify the specific PowerLogic device model (Pm5560, Pm5561, Pm5562, Pm5563, or PM8ECC) in your environment
- 2. Determine the current firmware version of the device through its web interface or management console
- 3. For PM5560: Download firmware version 2.7.8 or later from Schneider Electric's download portal (download.schneider-electric.com)
- 4. For PM5561: Download firmware version 10.7.3 or later from Schneider Electric's download portal
- 5. For PM5562: Download firmware version 2.5.5 or later from Schneider Electric's download portal
- 6. For PM5563: Download firmware version 2.7.8 or later from Schneider Electric's download portal
- 7. For PM8ECC: Contact Schneider Electric directly for available firmware updates - all versions are affected
- 8. Review Schneider Electric security notification for complete version details before upgrading
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22763 — 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-22763 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