# CVE-2026-97723: madpsy ka9q_ubersdr before 0.1.58 has a stored cross-site scripting (XSS) vulnerability in the chat message rendering functionality.


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-w3hg-374m-rvgx

## What is CVE-2026-97723?

CVE-2026-97723 is a medium-severity vulnerability in madpsy ka9q_ubersdr, published on 25 Sep 2026. 

### Official description

madpsy ka9q_ubersdr before 0.1.58 has a stored cross-site scripting (XSS) vulnerability in the chat message rendering functionality. User-controlled URLs in chat messages were insufficiently neutralized before being converted into HTML links. Quotation characters could break out of the generated href attribute and introduce attacker-controlled HTML attributes, allowing arbitrary JavaScript to execute in the browser of another user when the stored chat message was rendered. No click on the malicious link was required.

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

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


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

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

## Is CVE-2026-97723 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97723 is a medium-severity vulnerability in madpsy ka9q_ubersdr, published on 25 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-97723 in the wild and no public exploit code.

Affected product: madpsy ka9q_ubersdr. 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-97723/ (Markdown: https://insights.sbomify.com/CVE-2026-97723/index.md)
```

## Sources

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

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