dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-32107

HIGH · 8.0 CVSS v3.0 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
OS command injection vulnerability exists in Deco BE65 Pro firmware versions prior to "Deco BE65 Pro(JP)_V1_1.1.2 Build 20250123". If this vulnerability is exploited, an arbitrary OS command may be executed by the user who can log in to the device.

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

OS command injection vulnerability in Deco BE65 Pro router firmware allows authenticated users to execute arbitrary operating system commands. The vulnerability exists due to improper input validation in firmware versions prior to the patched build 20250123, enabling an attacker with valid login credentials to inject and execute OS-level commands on the device.

MitigationUpdate Deco BE65 Pro firmware to version 'Deco BE65 Pro(JP)_V1_1.1.2 Build 20250123' or later. Restrict administrative access to trusted personnel only and monitor for unauthorized access attempts.

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

CVSS:3.0/AV:A/AC:L/PR:L/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
    Log into the Deco web management interface or check the device label. Confirm the model is Deco BE65 Pro.
    Affected if Device is not a Deco BE65 Pro router, then this specific CVE does not apply.
  2. Locate the firmware version
    In the Deco web interface, navigate to Advanced > System > Firmware Update, or check under Advanced > System > Device Info. Note the displayed firmware build number.
    Affected if Unable to retrieve firmware version from the device interface.
  3. Compare firmware build to the patched version
    Compare the installed build number to 20250123. The vulnerability affects versions prior to (older than) build 20250123.
    Affected if Installed firmware build is less than 20250123 (for example, 20240115, 20231201, etc.).
  4. Confirm authentication is required
    Recall that this CVE requires valid administrative credentials. Verify whether the router admin interface is accessible over LAN or WAN and whether default or weak credentials may be in use.
    Affected if The device admin interface is exposed and uses default credentials or credentials known to unauthorized users, making the command injection exploitable.
  5. Review access logs for suspicious commands
    Check router logs (Advanced > System > Logs) for unexpected or malformed commands, especially those containing shell metacharacters like ; | & $ or backticks.
    Affected if Logs show commands or inputs that suggest exploitation of the command injection flaw.

The environment is affected if the device is a Deco BE65 Pro running firmware build lower than 20250123 and the admin interface is accessible with valid credentials.

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 Deco BE65 Pro firmware to version 'Deco BE65 Pro(JP)_V1_1.1.2 Build 20250123' or later. Restrict administrative access to trusted personnel only and monitor for unauthorized access attempts.

Recommended fix High confidence

Deco BE65 Pro(JP)_V1_1.1.2 Build 20250123

  1. 1. Download the firmware update "Deco BE65 Pro(JP)_V1_1.1.2 Build 20250123" from the official TP-Link support website (www.tp-link.com).
  2. 2. Access the Deco BE65 Pro device management interface through a web browser.
  3. 3. Navigate to the firmware upgrade section in the device settings.
  4. 4. Upload and apply the downloaded firmware file to update the device.
  5. 5. Verify the firmware version after update to confirm the patch was applied successfully.

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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