dbcve.org
N302r Plus FirmwareOperating system · Totolink

CVE-2025-5671

HIGH · 8.8 CVSS v3.1 Published 2025-06-05
Fix available
A fix is available. Upgrade to 3.4.0-b20201028 or later.
See remediation →
94/100
Remediation priority · Urgent
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
A vulnerability, which was classified as critical, was found in TOTOLINK N302R Plus up to 3.4.0-B20201028. Affected is an unknown function of the file /boafrm/formPortFw of the component HTTP POST Request Handler. The manipulation of the argument service_type leads to buffer overflow. It is possible to launch the attack 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

Buffer overflow vulnerability in TOTOLINK N302R Plus routers (firmware up to 3.4.0-B20201028) in the /boafrm/formPortFw HTTP POST handler. The service_type parameter is not properly bounds-checked before use in a fixed-size buffer, allowing remote attackers to overwrite memory and potentially execute arbitrary code via crafted HTTP requests.

MitigationApply vendor firmware update when available; until then, restrict administrative interface access to trusted networks or disable remote management to reduce attack surface.

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
N302r Plus FirmwareOperating system
Affected:< 3.4.0-b20201028

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

CVSS:3.1/AV:N/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 router model
    Log into the router web interface or check the device label/marketing materials to confirm the exact model is TOTOLINK N302R Plus
    Affected if The device is a TOTOLINK N302R Plus router
  2. Check the installed firmware version
    Access the router web interface (usually at 192.168.0.1 or 192.168.1.1), navigate to Status or System settings, and record the firmware version shown
    Affected if The firmware version is 3.4.0-B20201028 or any version prior to it (lower than 3.4.0-B20201028)
  3. Verify remote management is accessible
    Check the router web interface under Advanced or Security settings for 'Remote Management', 'Remote Access', or 'External Access' settings. Confirm whether HTTP/HTTPS management is enabled for WAN/outside networks
    Affected if Remote web management is enabled and accessible from outside the local network
  4. Test for vulnerable endpoint availability
    Send an HTTP POST request to the router's /boofrm/formPortFw endpoint (note: the path in the CVE is /boafrm/formPortFw). Use a tool like curl: curl -X POST -d 'service_type=test' http://<router-ip>/boafrm/formPortFw
    Affected if The router responds to requests at the /boafrm/formPortFw endpoint (indicating the vulnerable handler is present)

The device is affected if it is a TOTOLINK N302R Plus running firmware version 3.4.0-B20201028 or earlier AND the router's web interface is accessible remotely, exposing the vulnerable formPortFw handler.

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 3.4.0-b20201028 or later
Fixed in 3.4.0-b20201028
Interim mitigation

Apply vendor firmware update when available; until then, restrict administrative interface access to trusted networks or disable remote management to reduce attack surface.

Recommended fix Moderate confidence

N302R Plus Firmware version 3.4.0-b20201028 or later

  1. 1. Download the firmware version 3.4.0-b20201028 or later from the official TOTOLINK support website (www.totolink.net).
  2. 2. Access the router's web administration interface by entering the router's IP address in a web browser.
  3. 3. Log in with administrator credentials.
  4. 4. Navigate to the firmware upgrade or system settings section.
  5. 5. Upload the downloaded firmware file and initiate the upgrade process.
  6. 6. Wait for the upgrade to complete and the router to reboot.
  7. 7. After reboot, verify the firmware version in the router's admin panel to confirm the update was successful.
Caveat Minor: Router will reboot during upgrade; ensure stable power to avoid brick

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

Fix this in N302r Plus Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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