dbcve.org
Simatic Rtls Locating ManagerApplication · Siemens

CVE-2025-40751

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 3.3 or later.
See remediation →
80/100
Remediation priority · High
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 SIMATIC RTLS Locating Manager (All versions < V3.3). Affected SIMATIC RTLS Locating Manager Report Clients do not properly protect credentials that are used to authenticate to the server. This could allow an authenticated local attacker to extract the credentials and use them to escalate their access rights from the Manager to the Systemadministrator role.

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

SIMATIC RTLS Locating Manager Report Clients fail to properly protect stored credentials used for server authentication. An authenticated local attacker with Manager-level access can extract these credentials and use them to escalate privileges to the Systemadministrator role.

MitigationUpgrade SIMATIC RTLS Locating Manager to version V3.3 or later, which contains the fix for improper credential protection.

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
Simatic Rtls Locating ManagerApplication
Affected:< 3.3

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

CVSS:3.1/AV:L/AC:L/PR:L/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 SIMATIC RTLS Locating Manager version
    Open the SIMATIC RTLS Locating Manager application and navigate to Help > About, or check the installed program version via Windows Control Panel > Programs and Features. Look for the version number displayed.
    Affected if The installed version is listed as anything below V3.3 (for example, V3.2, V3.1, V3.0, or earlier).
  2. Confirm the Locating Manager service is running
    Open Windows Services (services.msc) and locate the service named 'SIMATIC RTLS Locating Manager' or similar. Verify its status is Running.
    Affected if The service is running and the application is actively used with stored server credentials for authentication.
  3. Check for Manager-level user accounts
    Within the SIMATIC RTLS Locating Manager application, navigate to the user management or administration section. Look for accounts assigned the Manager role level.
    Affected if Manager-level user accounts exist in the system, as these credentials could be extracted by a local attacker with Manager access.
  4. Inspect credential storage location
    Examine the application data directory for SIMATIC RTLS Locating Manager (typically under %ProgramData% or %AppData%). Look for configuration files, XML files, or databases that store server authentication credentials.
    Affected if Stored credentials are found in plaintext, weakly encrypted, or easily reversible format in configuration or database files accessible to local authenticated users.

You are affected if SIMATIC RTLS Locating Manager version is below V3.3 and the application stores server authentication credentials that could be accessed by an authenticated local user with Manager-level permissions.

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.3 or later
Fixed in 3.3
Interim mitigation

Upgrade SIMATIC RTLS Locating Manager to version V3.3 or later, which contains the fix for improper credential protection.

Recommended fix High confidence

V3.3

  1. Upgrade SIMATIC RTLS Locating Manager to version V3.3 or later to remediate the vulnerability.

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

Fix this in Simatic Rtls Locating Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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