dbcve.org
BroadlinkmanagerApplication · T0mer

CVE-2025-26320

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to after 5.9.1 or later.
See remediation →
74/100
Remediation priority · Elevated
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
t0mer BroadlinkManager v5.9.1 was discovered to contain an OS command injection vulnerability via the IP Address parameter at /device/ping.

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

BroadlinkManager v5.9.1 contains an OS command injection vulnerability in the /device/ping endpoint where the IP Address parameter is not properly sanitized before being passed to a system call. An attacker can inject arbitrary OS commands through this parameter, potentially gaining unauthorized access to the underlying system.

MitigationImplement strict input validation for the IP Address parameter using an allowlist approach, and replace any shell command execution with parameterized methods or safe API alternatives that do not invoke shell interpreters.

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
BroadlinkmanagerApplication
Affected:<= 5.9.1

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Identify BroadlinkManager installation
    Search for BroadlinkManager in your environment - check running processes, installed applications, or docker containers. Look for the application name 'BroadlinkManager' or 'broadlinkmanager'.
    Affected if BroadlinkManager is present in your environment
  2. Determine the installed version
    Check the version of BroadlinkManager by examining the application's about page, version file, docker image tag, or API endpoint that returns version information. Compare against the affected range <= 5.9.1.
    Affected if The installed version is 5.9.1 or any earlier version
  3. Verify /device/ping endpoint exists
    Attempt to access the /device/ping endpoint via HTTP GET or POST request to determine if the endpoint is exposed. This is typically found at http://[host]/device/ping.
    Affected if The /device/ping endpoint responds and accepts input
  4. Check for shell command execution in ping functionality
    Examine application logs, configuration, or source code if accessible. Look for evidence that the ping functionality invokes system shell commands rather than using safe API alternatives.
    Affected if The application uses shell execution (system(), exec(), popen(), or similar) to process the IP Address parameter in the ping endpoint

You are affected if BroadlinkManager version 5.9.1 or lower is installed and the /device/ping endpoint with shell-based command execution is accessible in your environment.

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 a release after 5.9.1
Interim mitigation

Implement strict input validation for the IP Address parameter using an allowlist approach, and replace any shell command execution with parameterized methods or safe API alternatives that do not invoke shell interpreters.

Recommended fix Moderate confidence

Latest available version > 5.9.1 (check GitHub releases for the current stable release)

  1. 1. Back up the current BroadlinkManager configuration and data
  2. 2. Stop the BroadlinkManager service
  3. 3. Download the latest version of BroadlinkManager from the official GitHub repository (github.com/t0mer/BroadlinkManager)
  4. 4. Install the updated version, ensuring it is newer than 5.9.1
  5. 5. Verify the /device/ping endpoint no longer accepts unsanitized input that could lead to OS command injection
  6. 6. Restart the BroadlinkManager service
  7. 7. Test that the ping functionality works correctly with valid IP addresses
  8. 8. Confirm the vulnerability is remediated by attempting injection via the IP parameter (should be sanitized or rejected)

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

Fix this in Broadlinkmanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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