# CVE-2026-0788: ALGO 8180 IP Audio Alerter Web UI Persistent Cross-Site Scripting Vulnerability

> Remote attackers can inject arbitrary scripts into the ALGO 8180 IP Audio Alerter web UI via the syslog viewer, allowing them to execute actions with target user privileges without authentication.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2026
- **Updated:** 23 Jan 2026
- **Also known as:** GHSA-xw4f-xqx2-q257

## What is CVE-2026-0788?

CVE-2026-0788 is a medium-severity cross-site scripting vulnerability in ALGO 8180 IP Audio Alerter, published on 23 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ALGO 8180 IP Audio Alerter Web UI Persistent Cross-Site Scripting Vulnerability. This vulnerability allows remote attackers to execute web requests with a target user's privileges on affected installations of ALGO 8180 IP Audio Alerter devices. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the functionality for viewing the syslog. The issue results from the lack of proper validation of user-supplied data, which can lead to the injection of an arbitrary script. An attacker can leverage this vulnerability to interact with the application in the context of the target user. Was ZDI-CAN-28298.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-0788?

It affects 1 product.


Products: Algosolutions 8180 Ip Audio Alerter Firmware.

## How do I fix CVE-2026-0788?

No fix has been published for CVE-2026-0788 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0788 being exploited?

There is no known exploitation of CVE-2026-0788 in the wild and no public exploit code.

## Other vulnerabilities in ALGO 8180 IP Audio Alerter

- [CVE-2026-0787](https://insights.sbomify.com/CVE-2026-0787/): ALGO 8180 IP Audio Alerter SAC Command Injection Remote Code Execution Vulnerability (high 8.1)
- [CVE-2026-0791](https://insights.sbomify.com/CVE-2026-0791/): ALGO 8180 IP Audio Alerter SIP INVITE Replaces Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.1)
- [CVE-2026-0792](https://insights.sbomify.com/CVE-2026-0792/): ALGO 8180 IP Audio Alerter SIP INVITE Alert-Info Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.1)
- [CVE-2026-0793](https://insights.sbomify.com/CVE-2026-0793/): ALGO 8180 IP Audio Alerter InformaCast Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 8.1)
- [CVE-2026-0794](https://insights.sbomify.com/CVE-2026-0794/): ALGO 8180 IP Audio Alerter SIP Use-After-Free Remote Code Execution Vulnerability (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0788 and fix it if it is affected.

What it is: CVE-2026-0788 is a medium-severity cross-site scripting vulnerability in ALGO 8180 IP Audio Alerter, published on 23 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0788 in the wild and no public exploit code.

Affected product: ALGO 8180 IP Audio Alerter. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0788/ (Markdown: https://insights.sbomify.com/CVE-2026-0788/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0788
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0788
- OSV: https://osv.dev/vulnerability/CVE-2026-0788

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0788/
Summaries are generated and may contain mistakes; the official description above is the record.