dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-7574

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-14
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, which was classified as critical, was found in LB-LINK BL-AC1900, BL-AC2100_AZ3, BL-AC3600, BL-AX1800, BL-AX5400P and BL-WR9000 up to 20250702. Affected is the function reboot/restore of the file /cgi-bin/lighttpd.cgi of the component Web Interface. The manipulation leads to improper authentication. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. 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 · high confidence

A critical improper authentication vulnerability exists in the LB-LINK router web interface CGI script (/cgi-bin/lighttpd.cgi), specifically in the reboot/restore function. The flaw allows remote attackers to bypass authentication and execute the reboot/restore function without valid credentials. This affects six models (BL-AC1900, BL-AC2100_AZ3, BL-AC3600, BL-AX1800, BL-AX5400P, BL-WR9000) running firmware up to July 2025. With a CVSS score of 9.8, the exploit requires no privileges or user interaction and can be executed remotely.

MitigationSince the vendor did not respond to disclosure and no patch is available, immediately restrict network access to the web interface via firewall rules or VLAN segmentation. Consider replacing affected devices with models from vendors that provide timely security updates. Monitor for indicators of compromise given the public exploit availability.

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
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 LB-LINK device model
    Access the router admin panel or check the device label/marketing materials to confirm the manufacturer is LB-LINK and note the model number.
    Affected if The device is an LB-LINK router with web management interface.
  2. Check if web interface is accessible
    Attempt to access http://<router-ip>/ or https://<router-ip>/ from the network. Look for the LB- LINK login page or any web-based management interface.
    Affected if The router exposes a web management interface on port 80 or 443.
  3. Verify CGI script presence
    Check if the endpoint /cgi-bin/lighttpd.cgi exists by accessing http://<router-ip>/cgi-bin/lighttpd.cgi. A 403 or 404 response indicates the path may or may not exist; a 500 error often indicates the script is present but executed without parameters.
    Affected if The /cgi-bin/lighttpd.cgi endpoint responds (any HTTP status code other than host unreachable or connection refused).
  4. Confirm WAN exposure of management interface
    Check router firewall settings or external port scan to determine if the web interface (port 80/443) is accessible from the WAN/internet rather than only from the LAN.
    Affected if The web management interface is reachable from WAN (internet-facing).
  5. Test reboot/restore function unauthenticated access
    Send a crafted request to /cgi-bin/lighttpd.cgi with reboot or restore parameters (e.g., GET/POST to the endpoint with relevant query parameters for reboot/restore) WITHOUT providing any authentication credentials. Observe if the device reboots or resets without being logged in.
    Affected if The device performs a reboot or factory restore action without requiring authentication credentials.

If the device is an LB-LINK router with an accessible web interface, especially if exposed to WAN, and the /cgi-bin/lighttpd.cgi endpoint allows unauthenticated reboot/restore actions, the environment is affected by CVE-2025-7574.

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

Since the vendor did not respond to disclosure and no patch is available, immediately restrict network access to the web interface via firewall rules or VLAN segmentation. Consider replacing affected devices with models from vendors that provide timely security updates. Monitor for indicators of compromise given the public exploit availability.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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