dbcve.org
CWE-620Weakness · CWE-620

CVE-2026-54801

HIGH · 7.2 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click 6 weeks old

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 vulnerability has been identified in CPCI85 Central Processing/Communication (All versions < V26.20), SICORE Base system (All versions < V26.20.0). The affected application contains insufficient validation of authentication credentials when processing administrative account modifications through the web API. This could allow an authenticated attacker to bypass security controls and gain unauthorized elevated 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 · moderate confidence

The vulnerability exists in the web API's validation of authentication credentials during administrative account modifications. An authenticated attacker can exploit insufficient validation logic to bypass security controls and elevate privileges to administrative levels.

MitigationUpgrade CPCI85 to version V26.20 or later and SICORE Base system to V26.20.0 or later. Alternatively, apply vendor-supplied security patches if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product version
    Locate and inspect the installed version of CPCI85 or SICORE Base system through the application's main interface, about page, or system information panel. If using command-line tools, run the appropriate version query command for your system.
    Affected if The installed version is below V26.20 for CPCI85 or below V26.20.0 for SICORE Base system.
  2. Confirm web API exposure
    Verify whether the web API service is accessible on your network by attempting to reach typical API endpoints (such as /api/, /webapi/, or the application's main URL) from an authorized internal location.
    Affected if The web API is accessible and responds to authentication requests.
  3. Check authentication module configuration
    Inspect the web API configuration files or administrative console to confirm whether the authentication validation module is enabled for administrative account modification functions.
    Affected if The authentication validation module is active and handles administrative account changes through the web API.
  4. Identify administrative account modification capability
    Review user role assignments and privilege settings within the application to determine if non-administrative accounts can access administrative account modification endpoints.
    Affected if Non-administrative authenticated users have access to or can reach administrative account modification functions via the web API.

You are affected if CPCI85 is below V26.20 or SICORE Base system is below V26.20.0, and the web API with administrative account modification capabilities is exposed and accessible to authenticated users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CPCI85 to version V26.20 or later and SICORE Base system to V26.20.0 or later. Alternatively, apply vendor-supplied security patches if available.

Recommended fix High confidence

V26.20 (or V26.20.0 for SICORE Base system)

  1. Identify the specific deployed product variant (CPCI85 Central Processing/Communication or SICORE Base system) in your environment
  2. Consult Siemens cert-portal.siemens.com for the official V26.20 or V26.20.0 patch/release
  3. Obtain the V26.20 (or V26.20.0) update package from Siemens official distribution channels
  4. Apply the update following Siemens standard upgrade procedures for the affected product
  5. Verify the update was successful and test administrative account modification functionality
  6. Confirm the patch addresses the insufficient authentication credential validation issue
Caveat Review Siemens release notes for V26.20.x for any compatibility or configuration changes before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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