dbcve.org
777vr1 FirmwareOperating system · Beetel

CVE-2026-2616

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-17
Fix available
A fix is available. Upgrade to after 01.00.09_55 or later.
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 has been found in Beetel 777VR1 up to 01.00.09. The impacted element is an unknown function of the component Web Management Interface. The manipulation leads to hard-coded credentials. The attack needs to be initiated within the local network. The exploit has been disclosed to the public and may be used. It is advisable to modify the configuration settings. The vendor was contacted early about this disclosure but did not respond in any way.

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

Hard-coded credentials vulnerability in Beetel 777VR1 router Web Management Interface (versions up to 01.00.09) allows attackers with local network access to gain unauthorized administrative access to the router configuration. The CVSS 9.8 score reflects the critical nature of credential-based authentication bypass.

MitigationChange default administrative credentials in the Web Management Interface and restrict access to the management interface to trusted IP addresses if possible; consider network segmentation to limit exposure.

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
777vr1 FirmwareOperating system
Affected:<= 01.00.09_55

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 router model
    Locate the device label on the Beetel 777VR1 router or check the web management interface login page for the model identifier
    Affected if The device is a Beetel 777VR1 router
  2. Check the firmware version
    Log into the router web interface and navigate to the Status or Administration page to view the firmware version. Compare it to the affected range: <= 01.00.09_55
    Affected if The firmware version is 01.00.09_55 or any earlier version
  3. Verify web management interface exposure
    Determine if the router web management interface (typically on port 80 or 443) is accessible from network segments outside of the trusted local network
    Affected if The web interface is accessible from untrusted network segments with local network access
  4. Confirm default credentials status
    Attempt to access the router using known default administrative credentials for this device model or check if credentials have been changed from factory defaults
    Affected if The default administrative credentials are still in use or unchanged

You are affected if you have a Beetel 777VR1 router running firmware version 01.00.09_55 or earlier, and the web management interface is accessible to untrusted network segments.

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 01.00.09_55
Interim mitigation

Change default administrative credentials in the Web Management Interface and restrict access to the management interface to trusted IP addresses if possible; consider network segmentation to limit exposure.

Recommended fix Low confidence
  1. Change the default administrative credentials for the web management interface immediately using the router's web UI or CLI
  2. If the router has a guest or separate network feature, enable it and segment trusted devices from the router management network
  3. Disable remote/web management access from WAN interfaces if this option is available in the router settings
  4. If possible, restrict access to the management interface to specific IP addresses via access control lists
  5. Consider replacing the device if no firmware updates are available, as hard-coded credentials typically cannot be fully remediated through configuration alone
  6. Monitor network traffic for unauthorized access attempts to the router's management interface

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

Fix this in 777vr1 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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