dbcve.org
8180 Ip Audio Alerter FirmwareOperating system · Algosolutions

CVE-2026-0790

HIGH · 7.5 CVSS v3.1 Published 2026-01-23
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
ALGO 8180 IP Audio Alerter Web UI Direct Request Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of ALGO 8180 IP Audio Alerter devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the web-based user interface. By navigating directly to a URL, a user can gain unauthorized access to data. An attacker can leverage this vulnerability to disclose information in the context of the device. Was ZDI-CAN-28299.

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

This is an unauthenticated information disclosure vulnerability in the ALGO 8180 IP Audio Alerter's web-based user interface. The flaw stems from a direct object reference issue where navigating to specific URLs directly bypasses authentication, allowing remote attackers to access sensitive data without any credentials.

MitigationApply any available vendor firmware updates for the ALGO 8180 device. If no patch exists, restrict network access to the device's web UI using firewall rules or network segmentation to prevent unauthorized external access.

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
8180 Ip Audio Alerter FirmwareOperating system
Affected:= 5.5

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. Confirm the device model and firmware version
    Access the web UI of the ALGO 8180 device and navigate to the About or Status page, or use SNMP to query the device for its firmware version string
    Affected if The firmware version is exactly 5.5 (Algosolutions 8180 Ip Audio Alerter Firmware)
  2. Verify the web interface is network accessible
    Attempt to reach the device's HTTP/HTTPS web interface from a location that should not have access (e.g., external network, untrusted VLAN) using curl or a browser
    Affected if The web interface responds to requests from untrusted network segments
  3. Test for authentication bypass on sensitive endpoints
    Send direct HTTP GET requests to suspected sensitive URLs (such as /config, /status, /logs, /backup, or similar paths that may contain device configuration or status data) without providing any authentication credentials
    Affected if Any sensitive endpoint returns valid data (configuration, logs, device status, credentials, or other sensitive information) without requiring a login session or credentials
  4. Compare your installed version to the affected range
    Document the exact firmware version displayed in the device web UI or obtained via SNMP, then compare it against the affected version 5.5
    Affected if Your device is running firmware version 5.5 and exhibits any of the unauthenticated access behaviors described above

You are affected if you have an ALGO 8180 device running firmware version 5.5 with its web UI accessible to untrusted networks and sensitive endpoints can be accessed without authentication.

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

Apply any available vendor firmware updates for the ALGO 8180 device. If no patch exists, restrict network access to the device's web UI using firewall rules or network segmentation to prevent unauthorized external access.

Fix this in 8180 Ip Audio Alerter Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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