dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-6225

MEDIUM · 6.9 CVSS v4.0 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Kieback&Peter Neutrino-GLT product is used for building management. It's web component "SM70 PHWEB" is vulnerable to shell command injection via login form. The injected commands would execute with low privileges. The vulnerability has been fixed in version 9.40.02

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

The SM70 PHWEB web component of Kieback&Peter Neutrino-GLT building management system contains a shell command injection vulnerability in the login form. Attackers can inject arbitrary OS commands through the login parameters, which execute on the underlying system with low privilege access.

MitigationUpdate the Neutrino-GLT product to version 9.40.02 or later to apply the vendor fix. As a defense-in-depth measure, restrict network access to the SM70 PHWEB interface and monitor for suspicious login patterns until patching is completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Neutrino-GLT installation
    Locate the Kieback&Peter Neutrino-GLT installation directory or check system services for the Neutrino-GLT or PHWEB components. On Windows, check Program Files; on Linux, check common application directories like /opt or /usr/local.
    Affected if The Neutrino-GLT software with SM70 PHWEB component is found on the system
  2. Check Neutrino-GLT version
    Look for version information in the software installation, typically in an About dialog, version file, or configuration files within the Neutrino-GLT installation directory. Compare the installed version against the fixed version 9.40.02.
    Affected if The installed version is earlier than 9.40.02 or the version cannot be determined
  3. Verify SM70 PHWEB is enabled
    Check if the SM70 PHWEB web interface component is configured and running. This is typically accessible via HTTP/HTTPS on a specific port. Verify the web service is active and accessible.
    Affected if The SM70 PHWEB web interface is exposed and running
  4. Check network exposure
    Determine if the PHWEB interface is accessible from network segments beyond the local network. Review firewall rules, NAT configurations, or reverse proxy settings that expose the web interface.
    Affected if The SM70 PHWEB interface is accessible from untrusted networks or the internet
  5. Review authentication logs
    Examine Neutrino-GLT and web server logs for unusual login patterns, failed authentication attempts with special characters in usernames, or unexpected command executions around the time of login events.
    Affected if Logs show login attempts containing shell metacharacters or unexpected command execution traces

A system is affected if it runs Neutrino-GLT with the SM70 PHWEB component at a version earlier than 9.40.02 and has the web interface exposed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Neutrino-GLT product to version 9.40.02 or later to apply the vendor fix. As a defense-in-depth measure, restrict network access to the SM70 PHWEB interface and monitor for suspicious login patterns until patching is completed.

Recommended fix High confidence

9.40.02

  1. Identify the current version of the Kieback&Peter Neutrino-GLT SM70 PHWEB component
  2. Obtain the fixed version 9.40.02 from Kieback&Peter
  3. Upgrade the SM70 PHWEB component to version 9.40.02
  4. Verify the upgrade was successful by checking the component version
  5. Test the login form functionality to confirm the command injection vulnerability is resolved
  6. Ensure the upgrade is deployed in accordance with Kieback&Peter's documentation and change management procedures

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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