Summary
OpenPanel before version 2.3.0 contains an unauthenticated server-side request forgery vulnerability in the site-checker endpoint. An attacker can provide a fully controlled URL to make the server contact internal services, localhost resources, or cloud metadata endpoints and disclose response-related information.
Affected context
The vulnerability occurs in deployments exposing the GET /tools/site-checker endpoint when the endpoint accepts arbitrary client-supplied URLs without sufficient destination validation. Risk is higher where the OpenPanel server can reach private network services, local interfaces, cloud metadata endpoints, or other privileged internal resources.
Exploit preconditions
- Attack surface: The publicly reachable GET /tools/site-checker endpoint
- Required access: No authentication may be required
- Trigger point: Processing of a client-controlled URL parameter
- Why exploitation is possible: The server makes outbound requests without reliably blocking private, loopback, link-local, or metadata destinations and without robust DNS-rebinding protections
Why this happens
The underlying bug is an insufficiently constrained server-side HTTP request feature. A user-controlled URL is passed to a server-side requester without enforcing an approved destination policy across resolution, connection, and redirect handling. This maps to CWE-918: Server-Side Request Forgery, where attackers can cause a server to access resources that are not intended to be directly reachable from the public attack surface.
Potential impact
- Attackers may access internal HTTP services
- Localhost or private network resources could be queried
- Cloud instance metadata or temporary credentials may be exposed
- Internal response titles, headers, status codes, or certificate details may be disclosed
- The vulnerable server could be used for network reconnaissance or limited internal-service interaction
General mitigation guidance
Mitigation generally focuses on reducing trust in user-supplied destinations and enforcing an explicit outbound request policy.
Common defensive patterns include:
- Allowing requests only to narrowly defined, approved external destinations
- Resolving hostnames and validating every resulting address against private, loopback, link-local, and metadata ranges
- Rechecking destinations after DNS resolution and before connection establishment
- Restricting redirects and validating each redirect target
- Blocking unnecessary egress from the application environment through network policy
- Running the service with minimal network and cloud permissions
- Avoiding exposure of detailed response metadata when it is not required
How teams detect issues like this
Organizations can identify SSRF risks through:
- Static analysis rules for HTTP clients receiving request parameters or other untrusted input
- Code review checks for missing private-address, redirect, and DNS-rebinding validation
- Tests covering loopback, private, link-local, metadata, IPv6, encoded-address, and rebinding scenarios
- Egress monitoring for unexpected requests from the OpenPanel process to internal or metadata endpoints
- Network policies that alert on or block unauthorized outbound destinations
- Automated security review tools that flag user-controlled URL fetches

