CVE-2022-26476
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 vulnerability has been identified in Spectrum Power 4 (All versions using Shared HIS), Spectrum Power 7 (All versions using Shared HIS), Spectrum Power MGMS (All versions using Shared HIS). An unauthenticated attacker could log into the component Shared HIS used in Spectrum Power systems by using an account with default credentials. A successful exploitation could allow the attacker to access the component Shared HIS with administrative privileges.
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 confidenceDefault credentials vulnerability in Shared HIS component used by Spectrum Power 4, 7, and MGMS allows unauthenticated remote attackers to gain administrative access to the component by using known default credentials.
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 dataall versionsall versionsall 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 Shared HIS component installationLocate the Shared HIS component within the Spectrum Power deployment. Check for files or services related to 'Shared HIS', 'HIS', or 'Hospital Information System' integration within the Spectrum Power installation directory or running services.Affected if Shared HIS component is present in the environment
-
Check for default administrative accountsReview the user account configuration within the Shared HIS component. Look for built-in administrative accounts that ship with default credentials. Compare account names against documentation or known default account listings.Affected if Default administrative accounts (such as admin, administrator, hisadmin, or similar built-in accounts) exist and have not been renamed or disabled
-
Verify credential changes from defaultsAudit all Shared HIS user accounts to confirm that passwords have been changed from vendor default values. This may require reviewing password policy settings, last password change dates, or attempting to identify default password patterns in any stored configuration.Affected if Any account passwords remain at vendor default values or follow predictable default patterns
-
Check for unauthorized admin-level accountsReview the list of accounts with administrative privileges in Shared HIS. Look for accounts that were not created by authorized administrators, especially those with full system access rights.Affected if Unauthorized or unknown accounts with administrative privileges exist in the system
-
Review remote access configurationExamine network configuration files and settings to determine if the Shared HIS component is exposed to remote network access. Check firewall rules, service bindings, and access control lists.Affected if Shared HIS is configured to accept remote connections from untrusted networks
The environment is affected if the Shared HIS component is present and any default administrative accounts remain with unchanged credentials or if unauthorized admin accounts exist.
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.
From vendor dataImmediately change all default credentials on Shared HIS components according to vendor guidance, disable remote access if not required, and verify no unauthorized accounts exist.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26476 — 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-2022-26476 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