CVE-2025-40772
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 SiPass integrated (All versions < V3.0). Affected server applications are vulnerable to stored Cross-Site Scripting (XSS), allowing an attacker to inject malicious code that can be executed by other users when they visit the affected page. Successful exploitation allows an attacker to impersonate other users within the application and steal their session data. This could enable unauthorized access to accounts and potentially lead to privilege escalation.
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 confidenceSiPass integrated versions prior to V3.0 contain a stored Cross-Site Scripting (XSS) vulnerability in the server application. An attacker can inject malicious script code into input fields that are stored on the server and rendered when other users access the affected page, enabling session hijacking and impersonation.
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< 3.00CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SiPass integrated installationLocate the SiPass integrated server application in your environment - typically installed on Windows servers as a physical access control system service. Check Program Files directory or service listings for 'SiPass integrated' or 'Sienaj' components.Affected if SiPass integrated is installed and running as a server application.
-
Check installed version numberAccess the SiPass integrated server console or admin interface, or check the installed software details via Windows Programs and Features. Look for the version displayed in the application (usually accessible via Help > About or system information page).Affected if The displayed version is below 3.00 (e.g., 2.x, 1.x).
-
Verify web interface accessibilityDetermine if the SiPass integrated web client or web portal is enabled and accessible. Check if HTTP/HTTPS ports for the web interface are open and responding.Affected if The web interface is enabled and reachable, providing user input fields.
-
Identify stored input fields in applicationNavigate to common data entry pages in the SiPass integrated interface such as user profiles, cardholder information, access rules, or system configuration fields where data is saved to the server database.Affected if Input fields exist that store user-supplied data to be rendered on subsequent page loads.
If SiPass integrated version is below 3.00 and the web interface with user input fields is accessible, the environment is affected by this stored XSS vulnerability.
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 · scoped3.00
Upgrade SiPass integrated to version V3.0 or later, which contains the vendor patch for this vulnerability. Until patching is complete, implement output encoding and input validation as compensating controls.
V3.0
- Identify the current version of SiPass Integrated installed on the system
- Consult the official Siemens support portal (cert-portal.siemens.com) for the V3.0 release package and upgrade documentation
- Review any pre-upgrade requirements such as backup procedures, system prerequisites, or migration guides
- Perform a complete backup of the current SiPass Integrated configuration and database
- Execute the upgrade procedure according to Siemens documentation to migrate to version 3.0
- Verify the upgrade was successful by checking the application version
- Confirm the XSS vulnerability is remediated by validating that user input is properly sanitized in the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40772 — 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-2025-40772 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