Summary
Openpanel contains an unauthenticated server-side request forgery (SSRF) vulnerability in the site-checker endpoint, which uses a user-controlled URL to make server-side HTTP requests without sufficient destination validation. A remote attacker may use this behavior to access internal services, query cloud metadata endpoints, scan network ports, and read limited response information.
Affected context
The vulnerability occurs in deployments exposing the site-checker API endpoint when its URL query parameter is accepted without effective SSRF controls. Risk is greater where the application can reach private network ranges, cloud instance metadata services, internal administration interfaces, or other systems that are not publicly accessible.
Exploit preconditions
- Attack surface: The unauthenticated GET /tools/site-checker endpoint - Required access: Network access to the exposed Openpanel API; application
authentication is not required
- Trigger point: Processing of a user-supplied URL query parameter - Why exploitation is possible: The server follows or fetches attacker-
selected destinations without adequate IP, hostname, redirect, or network
boundary validation, then returns response-derived information
Why this happens
The underlying bug is an SSRF design flaw in which externally supplied URL data is passed to a server-side request helper without first establishing that the destination is trusted and publicly routable. Missing validation of resolved addresses and redirects can allow requests to private, loopback, link-local, or otherwise restricted targets. This behavior maps to CWE-918, where an application is induced to send requests to unintended locations on behalf of an attacker.
Potential impact
- An attacker may retrieve cloud instance metadata or related credentials
- An attacker could probe internal services and network ports
- The application may disclose response status, size, timing, or parsed HTML metadata
- Internal IP addresses could be exposed through auxiliary IP lookup behavior
- Internal service details may support further intrusion or lateral movement
General mitigation guidance
Mitigation generally focuses on reducing trust in user-supplied destinations and enforcing an explicit outbound request policy. Common defensive patterns include validating and normalizing URLs before requests, resolving hostnames and checking every resulting address against private, loopback, link-local, and reserved ranges, and reapplying those checks after redirects. Secure defaults may restrict requests to an allowlist of approved schemes, hosts, and ports, or remove server-side fetching where it is not required. Outbound network policies, egress proxies, short timeouts, response-size limits, and least-privilege runtime permissions can reduce exposure if validation fails.
How teams detect issues like this
Detection approaches include static analysis for request helpers receiving direct query or body parameters, code review checks for missing hostname and IP-range validation, and tests covering redirects, DNS resolution changes, alternate address representations, and metadata endpoints. Network monitoring can identify unexpected egress to private ranges or cloud metadata services. Policy enforcement may require approved outbound destinations and block unrestricted server-side URL fetching. Automated security review tools can help identify likely SSRF data flows.

