dbcve.org
Sipass Integrated Ac5102 \(acc G2\) FirmwareOperating system · Siemens

CVE-2025-27494

HIGH · 7.2 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 6.4.9 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 AC5102 (ACC-G2) (All versions < V6.4.9), SiPass integrated ACC-AP (All versions < V6.4.9). Affected devices improperly sanitize input for the pubkey endpoint of the REST API. This could allow an authenticated remote administrator to escalate privileges by injecting arbitrary commands that are executed with root 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 confidence

This is a command injection vulnerability in the REST API's pubkey endpoint of SiPass integrated physical access control systems. An authenticated remote administrator can inject arbitrary OS commands through unsanitized input, which are then executed with root privileges, allowing full system compromise.

MitigationUpgrade SiPass integrated AC5102 and ACC-AP devices to firmware version V6.4.9 or later to obtain the patched REST API. If immediate patching is not feasible, restrict administrative access to the REST API to trusted IP addresses only.

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 Integrated Ac5102 \(acc G2\) FirmwareOperating system
Affected:< 6.4.9
Sipass Integrated Acc Ap FirmwareOperating system
Affected:< 6.4.9

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 the SiPass device model
    Access the system admin interface or check the physical device label to confirm the model is either AC5102 (acc G2) or ACC-AP.
    Affected if The device is a SiPass Integrated AC5102 or ACC-AP model.
  2. Check the installed firmware version
    Navigate to the system administration panel, typically found under System > Software or Device Information in the SiPass management interface. Locate the firmware version field.
    Affected if The firmware version is earlier than 6.4.9.
  3. Verify REST API accessibility
    Attempt to reach the REST API endpoint by accessing a URL such as https://<device-ip>/api/v1/ or similar API base path using a web browser or curl command.
    Affected if The REST API is accessible over the network.
  4. Confirm pubkey endpoint availability
    Send a GET request to the pubkey endpoint, typically at a path like /api/v1/pubkey or /rest/pubkey, using curl or similar tool: curl -k https://<device-ip>/api/v1/pubkey
    Affected if The pubkey endpoint responds (returns any HTTP status other than 404).

A user is affected if they have a SiPass Integrated AC5102 or ACC-AP device running firmware version lower than 6.4.9 with the REST API and pubkey endpoint exposed to the network.

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 6.4.9 or later
Fixed in 6.4.9
Interim mitigation

Upgrade SiPass integrated AC5102 and ACC-AP devices to firmware version V6.4.9 or later to obtain the patched REST API. If immediate patching is not feasible, restrict administrative access to the REST API to trusted IP addresses only.

Recommended fix High confidence

V6.4.9

  1. Obtain the firmware version 6.4.9 from the official Siemens cert-portal.siemens.com or authorized distribution channel
  2. Access the administrative interface of the affected Sipass Integrated AC5102 (ACC-G2) or ACC-AP device
  3. Navigate to the firmware upgrade or system maintenance section
  4. Upload and apply firmware version 6.4.9 following the vendor's documented upgrade procedure
  5. After upgrade completes, verify the firmware version is now V6.4.9 or higher
  6. Confirm the REST API pubkey endpoint now properly validates input

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

Fix this in Sipass Integrated Ac5102 \(acc G2\) Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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