/

CVE-2026-92815

Severity:

HIGH RISK

(7.5)

SSRF (CWE-918) in changedetection.io Browser Steps

CVE-2026-92815

Deferred

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-918

Impact:

Unauthorized access to internal network resources and potential information disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A server-side request forgery vulnerability in changedetection.io allows unauthenticated users to influence the destination of a browser-step "Goto URL" action. By supplying an internal URL through the optional action parameter, an attacker may retrieve responses from network locations that are not directly reachable from the public internet.

Affected context

The issue occurs in changedetection.io deployments that expose browser steps and fail to validate destinations supplied to the Goto URL action. Risk is higher when the application can reach private network services, cloud metadata endpoints, administrative interfaces, or other resources protected by network location rather than application authentication.

Exploit preconditions

  • Attack surface: The browser-step Goto URL action exposed through the application
  • Required access: No authentication may be required when the affected action is reachable by an attacker
  • Trigger point: Processing of a user-controlled optional_value used as a navigation target
  • Why exploitation is possible: Insufficient destination validation allows the server-side browser to request arbitrary internal addresses and return or expose their responses

Why this happens

The underlying flaw is inadequate validation of a user-controlled URL before it is used by a server-side browser component. This maps to CWE-918: Server-Side Request Forgery, where application-controlled network requests can be redirected to attacker-selected destinations. The insecure pattern is trusting a supplied URL without enforcing an approved scheme, host, address range, redirect policy, and network boundary.

Potential impact

  • An attacker may retrieve sensitive responses from internal services
  • Internal administrative interfaces could be exposed
  • Cloud or platform metadata may be accessible where network controls permit it
  • The application could be used to probe private network topology
  • Obtained credentials or tokens could enable further compromise

General mitigation guidance

Mitigation generally focuses on reducing trust in user-supplied destinations and constraining server-side network access.

Common defensive patterns include:

  • Restricting navigation to an explicit allowlist of approved schemes and hosts
  • Blocking loopback, link-local, private, reserved, and local network address ranges
  • Revalidating destinations after DNS resolution and across redirects
  • Applying egress firewall policies that limit application connectivity
  • Separating browser workers from sensitive internal networks
  • Running the service with only the network and application privileges it requires
  • Avoiding exposure of response bodies from destinations that are not explicitly trusted

How teams detect issues like this

Organizations can identify SSRF risks through:

  • Static analysis rules for user-controlled URLs passed to browser, HTTP, or network-request APIs
  • Code review checks for missing scheme, hostname, IP-range, redirect, and DNS-rebinding validation
  • Dynamic testing with requests targeting loopback, private, link-local, and metadata address ranges
  • Network monitoring for unexpected outbound connections from browser workers
  • Egress policies and alerts for access to internal service ranges
  • Automated security review tools that flag server-side requests using untrusted destinations

Sources

SourceLink
github.comgithub.com/dgtlmoon/changedetection.io
github.comgithub.com/dgtlmoon/changedetection.io/blob/0.60.6/changedetectionio/browser_steps/browser_steps.py#L182-L192
github.comgithub.com/geo-chen/oss/blob/main/changedetection.io.md#finding-2-ssrf-via-browser-step-goto-url-action-bypasses-the-ssrf-guard-guard-only-applied-to-the-main-watch-url
vulncheck.comvulncheck.com/advisories/changedetection-io-through-0.60.6-ssrf-via-browser-step-goto-url

Frequently asked

questions

It may be remotely exploitable without authentication when the affected browser-step functionality is publicly reachable and accepts attacker-controlled action parameters.

The key requirement is access to invoke the vulnerable action. No authenticated account may be necessary in configurations where the action endpoint is exposed anonymously.

Use a strict destination allowlist, block private and special-purpose address ranges, validate resolved addresses, and control redirects and outbound network access.

Treat all user-provided URLs as untrusted, enforce centralized URL validation, apply least-privilege egress policies, and monitor server-side components for unexpected internal requests.

Find out what's already
exploitable in your codebase.