Missing AuthenticationWeakness · CWE-306

CVE-2025-59780

HIGH · 7.5 CVSS v3.1 Published 2025-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
General Industrial Controls Lynx+ Gateway is missing critical authentication in the embedded web server which could allow an attacker to send GET requests to obtain sensitive device information.

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

The General Industrial Controls Lynx+ Gateway has a critical authentication bypass vulnerability in its embedded web server. Attackers can send unauthenticated GET requests to access sensitive device information without any credentials, indicating the web server fails to enforce authentication checks on certain endpoints.

MitigationImplement proper authentication enforcement on all web server endpoints, requiring valid credentials for any access to sensitive device information. Consider network segmentation to limit exposure of the device management interface.

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
None
Availability
None

CVSS:3.1/AV:N/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 the Lynx+ Gateway device
    Locate and confirm the General Industrial Controls Lynx+ Gateway in your network inventory. Check device labeling, network documentation, or use network scanning to identify the device by its hostname or MAC vendor prefix.
    Affected if The device is a General Industrial Controls Lynx+ Gateway.
  2. Determine if the embedded web server is running
    Use a network scanner (such as nmap) to check if TCP ports 80 or 443 (HTTP/HTTPS) are open on the device IP address. Alternatively, attempt to curl or browse to http://<device-ip>/ to see if a web interface responds.
    Affected if The web server is accessible on the device and responds to HTTP/HTTPS requests.
  3. Test for unauthenticated endpoint access
    Send a GET request to common sensitive endpoints without providing any credentials. Examples: curl -v http://<device-ip>/status, curl -v http://<device-ip>/config, or curl -v http://<device-ip>/deviceinfo. Observe whether the server returns data without prompting for login.
    Affected if The web server returns sensitive device information (status, config, device info) without requiring any authentication credentials.
  4. Check for authentication enforcement
    Attempt to access the same endpoints using invalid or empty credentials. Observe if the server denies access or redirects to a login page. A vulnerable device will return data without any authentication challenge.
    Affected if No login prompt or authentication challenge appears, and data is returned directly.
  5. Compare installed firmware version
    If accessible, check the device firmware version through the web interface or by querying the /about or /version endpoint. Compare this version against any official version guidance from General Industrial Controls.
    Affected if The firmware version is at or below the version where the vulnerability was addressed (if known).

If the Lynx+ Gateway web server returns sensitive device information via unauthenticated GET requests without requiring any login credentials, the environment is affected by CVE-2025-59780.

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

Implement proper authentication enforcement on all web server endpoints, requiring valid credentials for any access to sensitive device information. Consider network segmentation to limit exposure of the device management interface.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-59780 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