dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-34319

CRITICAL · 9.3 CVSS v4.0 Published 2025-12-03
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
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
TOTOLINK N300RT wireless router firmware versions prior to V3.4.0-B20250430 (discovered in V2.1.8-B20201030.1539) contain an OS command injection vulnerability in the Boa formWsc handling functionality. An unauthenticated attacker can send specially crafted requests to trigger command execution via the targetAPSsid request parameter.

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 TOTOLINK N300RT wireless router firmware's Boa web server formWsc functionality allows unauthenticated remote attackers to execute arbitrary OS commands via the targetAPSsid request parameter.

MitigationUpgrade firmware to V3.4.0-B20250430 or later; if immediate patching is not possible, restrict WAN access to the router's web management interface to prevent external exploitation.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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. Identify device model
    Access the router admin interface or check the device label; confirm the model is TOTOLINK N300RT
    Affected if Device is not a TOTOLINK N300RT router (different models are not affected by this specific CVE)
  2. Determine firmware version
    Log into the router web interface (usually at 192.168.0.1), navigate to System Status or Firmware Upgrade page, and record the firmware version string
    Affected if Firmware version is earlier than V3.4.0-B20250430 (versions prior to this patch are vulnerable)
  3. Verify Boa web server accessibility
    Attempt to access the router's HTTP/HTTPS web interface from the network perspective you want to protect (port 80 or 443)
    Affected if The web management interface is accessible from untrusted networks (this is the attack vector for the unauthenticated command injection)
  4. Check WPS functionality status
    In the router admin panel, locate WPS or WSC (Wi-Fi Protected Setup) settings; determine if this feature is enabled
    Affected if WPS/WSC is enabled and the formWsc handler is active (this is the specific vulnerable component)

You are affected if you have a TOTOLINK N300RT router running firmware earlier than V3.4.0-B20250430 with the web interface accessible and WPS feature enabled.

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 firmware to V3.4.0-B20250430 or later; if immediate patching is not possible, restrict WAN access to the router's web management interface to prevent external exploitation.

Recommended fix High confidence

TOTOLINK N300RT firmware V3.4.0-B20250430 or later

  1. 1. Identify all TOTOLINK N300RT wireless routers in your network inventory
  2. 2. Access the router's web administration interface (typically http://192.168.0.1)
  3. 3. Navigate to the firmware upgrade or system settings section to check the current firmware version
  4. 4. Download the fixed firmware version V3.4.0-B20250430 (or later) from the official TOTOLINK website (totolink.net or totolink.tw)
  5. 5. In the router admin panel, upload the downloaded firmware file and initiate the upgrade
  6. 6. Wait for the router to reboot and apply the new firmware
  7. 7. After reboot, verify the firmware version displays as V3.4.0-B20250430 or later
  8. 8. Confirm the upgrade was successful and test router functionality
Caveat Standard firmware update; backup router configuration before upgrading as a precaution

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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