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_valueused 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

