# CVE-2026-92814: changedetection.io through 0.60.6 Cross-Site Scripting via watch_title

> Attackers can inject malicious scripts into notification templates via scraped page titles, potentially compromising users who view these notifications.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-99x5-c87r-97w2

## What is CVE-2026-92814?

CVE-2026-92814 is a low-severity cross-site scripting vulnerability in dgtlmoon changedetection.io, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

changedetection.io through 0.60.6 fails to escape the scraped page title in HTML notifications, allowing arbitrary markup injection. Attackers can place malicious markup in monitored page titles that reaches notification channels like email and Telegram as live content when the watch_title token is used in templates.

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

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


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

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

## Is CVE-2026-92814 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92814 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92814 is a low-severity cross-site scripting vulnerability in dgtlmoon changedetection.io, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92814 exists.

Affected product: dgtlmoon changedetection.io. 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-92814/ (Markdown: https://insights.sbomify.com/CVE-2026-92814/index.md)
```

## Sources

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

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