dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-27804

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
Several OS command injection vulnerabilities exist in the device firmware in the /var/salia/mqtt.php script. By publishing a specially crafted message to a certain MQTT topic arbitrary OS commands can be executed with root permissions.

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

OS command injection vulnerability in /var/salia/mqtt.php allows attackers to execute arbitrary OS commands with root privileges by publishing specially crafted messages to a specific MQTT topic.

MitigationRestrict access to the MQTT broker and topics; apply vendor firmware patches when available; if no patch exists, sanitize all MQTT message inputs in mqtt.php or implement network segmentation to limit exposure.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

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. Verify if /var/salia/mqtt.php exists on your system
    Run: ls -la /var/salia/mqtt.php or find / -path '*/salia/mqtt.php' 2>/dev/null
    Affected if The file exists - the vulnerable component is present on this system
  2. Confirm if the MQTT broker service is running
    Run: systemctl status mosquitto or ps aux | grep mqtt
    Affected if The MQTT broker is running and accessible over the network or locally to untrusted users
  3. Identify the MQTT topic that triggers mqtt.php processing
    Inspect the mqtt.php source code: grep -i 'subscribe\|topic' /var/salia/mqtt.php to find the subscription pattern
    Affected if The topic is wildcarded or accessible to unauthenticated clients
  4. Check MQTT broker access controls and authentication
    Review broker config: cat /etc/mosquitto/conf.d/*.conf or grep -r 'allow_anonymous\|acl' /etc/mosquitto/
    Affected if allow_anonymous is set to true OR no ACL rules are defined to restrict topic access
  5. Test if arbitrary commands can be injected via the MQTT topic
    Use a test client (mosquitto_pub) to publish a payload containing shell metacharacters like $(whoami) or ;ls to the identified topic
    Affected if The payload is processed by mqtt.php and results in command execution

You are affected if /var/salia/mqtt.php exists AND the MQTT broker is running with the vulnerable topic accessible to untrusted parties.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the MQTT broker and topics; apply vendor firmware patches when available; if no patch exists, sanitize all MQTT message inputs in mqtt.php or implement network segmentation to limit exposure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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