Categories
CVE-2026-27645

Cross-Site Scripting (XSS) in changedetection-io (CVE-2026-27645)

Summary

Cross-site scripting in changedetection-io (CVE-2026-27645). Risk of unauthorized operations or information disclosure. Exploitable via GET /rss/watch/. Mitigation: upgrade to 0.53.7 or later.

Original description

The description as published by the source.

changedetection.io is a free open source web page change detection tool. In versions prior to 0.54.1, the RSS single-watch endpoint reflects the UUID path parameter directly in the HTTP response body without HTML escaping. Since Flask returns text/html by default for plain string responses, the browser parses and executes injected JavaScript. Version 0.54.1 contains a fix for the issue.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-27645 has been found in changedetection-io.
Attackers can target a specific entry point like GET /rss/watch/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade changedetection-io to 0.53.7 or later.
If unsure, ask your IT team or search "changedetection-io CVE-2026-27645" on the vendor's site.

CVE-2026-27645 (changedetection-io) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: GET /rss/watch/
Patched: 0.53.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in changedetection-io. Attackers reach the vulnerable code path via GET /rss/watch/ without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of changedetection-io. Attack surface: GET /rss/watch/.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.53.7.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /rss/watch/ requests with malformed payloads or SQL meta-characters. Run grep -r 'changedetection-io' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'changedetection-io' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で changedetection-io を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'GET /rss/watch/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /rss/watch/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade changedetection-io to 0.53.7

    ステージング環境で 0.53.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against GET /rss/watch/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI changedetection-io
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.53.7"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details