dbcve.org
Router FirmwareOperating system · Bectechnologies

CVE-2025-2772

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
BEC Technologies Multiple Routers Insufficiently Protected Credentials Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of BEC Technologies routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within /cgi-bin/tools_usermanage.asp. The issue results from transmitting a list of users and their credentials to be handled on the client side. An attacker can leverage this vulnerability to disclose transported credentials, leading to further compromise. Was ZDI-CAN-25895.

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

The vulnerability exists in /cgi-bin/tools_usermanage.asp on BEC Technologies routers. The page transmits a list of users and their credentials directly to the client side without requiring authentication. Network-adjacent attackers can access this endpoint to retrieve plaintext credentials, enabling full compromise of router accounts.

MitigationRestrict network access to the router management interface from untrusted networks. Contact BEC Technologies for firmware updates. If a patch is unavailable, consider network segmentation to limit exposure to adjacent attackers.

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
Router FirmwareOperating system
Affected:all versions

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 if the device is a BEC Technologies router
    Check the router's web interface or label for the vendor name 'BEC Technologies' or model number. You can also inspect HTTP response headers from the router's web server for 'BEC' or 'Bectechnologies' in the Server or X-Powered-By headers.
    Affected if The device is a BEC Technologies router and is accessible on the network.
  2. Confirm the router's web interface is network-accessible
    Attempt to reach the router's default management IP address over HTTP (port 80) or HTTPS (port 443) from a network-adjacent position. Ensure you have network connectivity to the router's LAN or WAN interface depending on deployment.
    Affected if The router's web interface responds to HTTP/HTTPS requests.
  3. Access the vulnerable endpoint without credentials
    Send an HTTP GET request to http://<router_ip>/cgi-bin/tools_usermanage.asp without providing any authentication cookies, headers, or credentials. Use a tool like curl: curl -v http://<router_ip>/cgi-bin/tools_usermanage.asp
    Affected if The endpoint returns an HTTP 200 response without requiring any authentication.
  4. Inspect response for exposed credentials
    Examine the HTTP response body from the /cgi-bin/tools_usermanage.asp endpoint. Look for plaintext usernames and passwords, user account lists, or credential-related fields in the HTML or JSON response.
    Affected if The response contains plaintext user credentials, password fields, or account information without having authenticated first.

If the /cgi-bin/tools_usermanage.asp endpoint is accessible and returns user account credentials without requiring authentication, the environment is affected by CVE-2025-2772.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the router management interface from untrusted networks. Contact BEC Technologies for firmware updates. If a patch is unavailable, consider network segmentation to limit exposure to adjacent attackers.

Fix this in Router Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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