dbcve.org
Ozw672 FirmwareOperating system · Siemens

CVE-2025-26389

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 8.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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 OZW672 (All versions < V8.0), OZW772 (All versions < V8.0). The web service in affected devices does not sanitize the input parameters required for the `exportDiagramPage` endpoint. This could allow an unauthenticated remote attacker to execute arbitrary code 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

Command injection vulnerability in the web service of OZW672 and OZW772 devices. The `exportDiagramPage` endpoint does not sanitize input parameters, allowing unauthenticated remote attackers to execute arbitrary code with root privileges.

MitigationUpdate affected devices to firmware version V8.0 or later to obtain the vendor patch. If immediate patching is not possible, restrict network access to the web service interface or disable it if not required.

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
Ozw672 FirmwareOperating system
Affected:< 8.0
Ozw772 FirmwareOperating system
Affected:< 8.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 device model
    Access the device web interface or use network scanning to confirm the device is specifically an OZW672 or OZW772 unit. Check the device information page or system status page for the exact model designation.
    Affected if The device model is OZW672 or OZW772 and is not a later/replacement model.
  2. Check the installed firmware version
    Locate the firmware version information in the device web interface (typically under System, Device Info, or About sections). Compare the version number to the affected range of versions prior to 8.0.
    Affected if The installed firmware version is below version 8.0 (for example, V7.x, V6.x, etc.).
  3. Verify the web service is accessible
    Confirm the device web service interface is reachable over the network on typical HTTP/HTTPS ports (80/443 or custom ports). Use a browser or curl command to confirm the login page or status page is accessible.
    Affected if The web service interface is exposed and reachable on the network.
  4. Confirm the vulnerable endpoint exists
    Probe for the exportDiagramPage endpoint by accessing a URL path such as /exportDiagramPage or checking the web application sitemap if available. The endpoint should respond (even with an error) to indicate it exists.
    Affected if The exportDiagramPage endpoint responds to requests, indicating it is present in the web service.

The device is affected if it is an OZW672 or OZW772 with firmware version below 8.0 and the web service with the exportDiagramPage endpoint is accessible.

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

Update affected devices to firmware version V8.0 or later to obtain the vendor patch. If immediate patching is not possible, restrict network access to the web service interface or disable it if not required.

Recommended fix High confidence

OZW672/OZW772 Firmware V8.0

  1. 1. Identify the current firmware version of the OZW672 or OZW772 device via the web interface or device management console
  2. 2. Navigate to the official Siemens support portal and download the V8.0 firmware update for your specific device model
  3. 3. Backup the current device configuration through the web interface or management interface
  4. 4. Access the device's firmware update or administration section in the web interface
  5. 5. Upload the V8.0 firmware file and initiate the update process
  6. 6. Wait for the firmware update to complete (do not power off the device during this process)
  7. 7. After the device restarts, verify the new firmware version is displayed as V8.0 or later
  8. 8. Restore the backed-up configuration if necessary
Caveat Review Siemens release notes for V8.0 for any configuration or feature changes that may require adjustment

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

Fix this in Ozw672 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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