dbcve.org
Ca300 Poe FirmwareOperating system · Totolink

CVE-2025-6619

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
A vulnerability was found in TOTOLINK CA300-PoE 6.2c.884. It has been declared as critical. Affected by this vulnerability is the function setUpgradeFW of the file upgrade.so. The manipulation of the argument FileName leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

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

A critical OS command injection vulnerability exists in TOTOLINK CA300-PoE firmware 6.2c.884 in the setUpgradeFW function within upgrade.so. The FileName parameter is not sanitized before being passed to system calls, allowing remote attackers to execute arbitrary OS commands by injecting shell metacharacters.

MitigationThis device is end-of-life with no vendor patch available. Organizations should replace the device with a supported model or implement strict network segmentation and firewall rules to restrict all access to the device management interface.

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
Ca300 Poe FirmwareOperating system
Affected:= 6.2c.884

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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
    Check the device label, web interface, or SNMP to confirm it is a TOTOLINK CA300-PoE device
    Affected if Device is not a TOTOLINK CA300-PoE, then not affected by this specific CVE
  2. Check the firmware version
    Access the device web interface (typically http://192.168.0.1) and navigate to System Status or Firmware Upgrade to view the installed firmware version
    Affected if Firmware version is exactly 6.2c.884, then the device is vulnerable
  3. Verify the upgrade.so module exists
    Check the device firmware by examining /lib/upgrade.so or similar paths via telnet/ssh if available, or compare firmware file contents
    Affected if The upgrade.so library with the setUpgradeFW function exists on the device, the vulnerability is present
  4. Confirm device is network accessible
    Ping the device IP and verify the web management interface is reachable on ports 80/443
    Affected if The device management interface is exposed to untrusted networks, the command injection can be exploited remotely
  5. Check for external exposure
    Review firewall rules and network boundary devices to determine if the device management interface (HTTP/HTTPS) is accessible from the internet or untrusted VLANs
    Affected if The device is directly accessible from the internet or untrusted networks, it is at highest risk of exploitation

A TOTOLINK CA300-PoE device running firmware version 6.2c.884 with its management interface exposed to the network is affected by this command injection vulnerability.

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

This device is end-of-life with no vendor patch available. Organizations should replace the device with a supported model or implement strict network segmentation and firewall rules to restrict all access to the device management interface.

Recommended fix Low confidence

Latest available CA300-PoE firmware from TOTOLINK (verify version > 6.2c.884)

  1. 1. Visit the official TOTOLINK support website at www.totolink.net to check for firmware updates
  2. 2. Locate the CA300-PoE product page and download the latest available firmware version
  3. 3. Access the device web interface and navigate to the firmware upgrade section
  4. 4. Upload and apply the new firmware version following the manufacturer's instructions
  5. 5. After upgrade, verify the firmware version displayed matches the expected fixed version
  6. 6. Consider changing administrator credentials as a precaution since command injection may have allowed credential compromise
Caveat Review release notes for any configuration reset requirements or feature changes before upgrading

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

Fix this in Ca300 Poe Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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