dbcve.org
Sipass IntegratedApplication · Siemens

CVE-2025-40773

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 3.00 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 SiPass integrated (All versions < V3.0). Affected server applications contains a broken access control vulnerability. The authorization mechanism lacks sufficient server-side checks, allowing an attacker to execute a specific API request. Successful exploitation allows an attacker to potentially manipulate data belonging to other users.

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

SiPass integrated versions prior to V3.0 contain a broken access control vulnerability in the server applications. The authorization mechanism fails to perform sufficient server-side validation, allowing an attacker to execute specific API requests and potentially manipulate data belonging to other users.

MitigationUpgrade SiPass integrated to version V3.0 or later to obtain the patched authorization mechanisms. Since this is a server-side access control issue, ensure post-upgrade testing verifies that cross-user data isolation is properly enforced.

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
Sipass IntegratedApplication
Affected:< 3.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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify SiPass integrated is installed
    Check for SiPass integrated installation directory, typically found under C:\Program Files\SiPass or C:\Program Files (x86)\SiPass. Look for siPass.exe or related server executable files.
    Affected if SiPass integrated server application is found on the system
  2. Determine the installed version
    Right-click on the siPass.exe or main server executable, select Properties, then check the Details tab for version information. Alternatively, open the SiPass client and look for the version displayed in the About or System Info section.
    Affected if The version displayed is prior to V3.0 (e.g., 2.x.x or any version number less than 3.00)
  3. Identify if server services are running
    Open Windows Services (services.msc) and look for SiPass-related services such as SiPass Server, SiPass Integrated Server, or similar. Check if the service status is Running.
    Affected if The SiPass server service is installed and running
  4. Check for exposed API accessibility
    If the server is accessible over network, attempt to reach common SiPass API endpoints or verify the web interface port is open. Common ports include 443 or 8080 for SiPass web interfaces. Use netstat or port scanning to confirm the server is listening.
    Affected if The SiPass server API/web interface is accessible (port is open and responding)
  5. Verify user isolation configuration
    Log into the SiPass administrative interface with a standard user account and attempt to access or modify data belonging to a different user account. Document whether cross-user data access is possible without proper authorization.
    Affected if A user can access or modify data belonging to other users without proper authorization checks

The environment is affected if SiPass integrated server is installed with a version prior to V3.0 and the server service is running, exposing the vulnerable authorization mechanism to 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
Upgrade available Upgrade to 3.00 or later
Fixed in 3.00
Interim mitigation

Upgrade SiPass integrated to version V3.0 or later to obtain the patched authorization mechanisms. Since this is a server-side access control issue, ensure post-upgrade testing verifies that cross-user data isolation is properly enforced.

Recommended fix High confidence

V3.0

  1. Identify the current version of SiPass Integrated currently installed
  2. Confirm the installed version is below V3.0 (vulnerable)
  3. Obtain the V3.0 upgrade package from Siemens official support portal (cert-portal.siemens.com) or contact Siemens customer support
  4. Review Siemens release notes and upgrade documentation for V3.0
  5. Execute the upgrade process following Siemens-provided upgrade instructions
  6. After upgrade, verify the installed version is V3.0 or higher
  7. Test that the authorization mechanisms are functioning correctly
Caveat Review Siemens release notes for V3.0 to check for any breaking changes or migration requirements before upgrading

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

Fix this in Sipass Integrated Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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