Command InjectionWeakness · CWE-77

CVE-2025-41451

HIGH · 8.7 CVSS v4.0 Published 2025-08-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable

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
Improper neutralization of alarm-to-mail configuration fields used in an OS shell Command ('Command Injection') in Danfoss AK-SM8xxA Series prior to version 4.3.1, leading to a potential post-authenticated remote code execution on an attacked system.

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

The Danfoss AK-SM8xxA Series HVAC controller devices contain a command injection vulnerability in alarm-to-mail configuration fields. An authenticated attacker can inject OS commands through improperly sanitized configuration inputs, potentially executing arbitrary code on the device.

MitigationUpgrade Danfoss AK-SM8xxA Series devices to version 4.3.1 or later to remediate this vulnerability.

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
High
Privileges
High
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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. Confirm device model is AK-SM8xxA Series
    Access the device web interface or system information page and verify the model number matches the Danfoss AK-SM8xxA Series product line.
    Affected if Device is not an AK-SM8xxA Series model - not affected
  2. Check installed firmware version
    Navigate to the device firmware or system information section in the admin interface and note the displayed version number.
    Affected if Firmware version is 4.3.1 or later - not affected; version prior to 4.3.1 indicates potential vulnerability
  3. Verify alarm-to-mail feature is configured
    Locate the alarm-to-mail settings in the device configuration and check whether any email recipients or mail server fields are defined.
    Affected if Alarm-to-mail feature is not configured - exploitation requires this feature to be set up
  4. Assess authentication exposure
    Review the user accounts with access to the device admin panel and confirm whether credentials are strong and not default.
    Affected if Attacker needs valid credentials to exploit this vulnerability; weak or compromised credentials increase risk

Device is affected if it is a Danfoss AK-SM8xxA Series model running firmware version prior to 4.3.1 with alarm-to-mail feature configured and accessible to an authenticated attacker.

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

Upgrade Danfoss AK-SM8xxA Series devices to version 4.3.1 or later to remediate this vulnerability.

Recommended fix High confidence

version 4.3.1 or later of Danfoss AK-SM8xxA Series firmware

  1. Identify all Danfoss AK-SM8xxA Series devices in the environment and note their current firmware versions
  2. Access the device management interface and navigate to the firmware update or system maintenance section
  3. Obtain firmware version 4.3.1 or later from the official Danfoss support portal (www.danfoss.com)
  4. Follow Danfoss's published firmware upgrade procedure for the AK-SM8xxA series - this typically involves uploading the firmware file through the web-based management interface
  5. After completing the firmware update, verify the device reports version 4.3.1 or later
  6. Confirm the alarm-to-mail configuration functionality is operational after the upgrade
  7. Document the update in the asset inventory for audit and compliance purposes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41451 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