Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2025-56563 – Unauthenticated SSRF – Zenith Satellite Tracker 1.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2025-56563 is a critical Server-Side Request Forgery (SSRF) vulnerability affecting Zenith Satellite Tracker 1.0. The flaw resides in the sat_proxy.php endpoint, which forwards attacker-controlled URLs to an internal cURL request without any validation, allowing an unauthenticated remote attacker to force the server to issue arbitrary HTTP/HTTPS requests. The issue carries a CVSS v3.1 base score of 9.8 (Critical) due to its unauthenticated, network-exploitable nature and its potential for total confidentiality, integrity, and availability impact.

Technical details

  • Root cause: The address GET parameter supplied to api/sat_proxy.php is passed directly to a cURL request (CURLOPT_URL) with no validation of scheme, host, resolved IP address, or port.
  • Trigger conditions: A single unauthenticated HTTP GET request to the sat_proxy.php endpoint with an attacker-supplied address value is sufficient to trigger the flaw.
  • Attack vector: Network-based, requiring no authentication and no user interaction (AV:N, PR:N, UI:N).
  • Impact: The vulnerable proxy can be abused to reach internal-only services (e.g., 127.0.0.1, private RFC1918 ranges) and cloud instance metadata endpoints, enabling internal network reconnaissance, port scanning, and potential disclosure of sensitive credentials or configuration data reachable only from the server’s network position.

Affected software

  • Zenith Satellite Tracker 1.0 (all installations exposing api/sat_proxy.php)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No official patched version has been published by the vendor at this time; organizations running Zenith Satellite Tracker 1.0 should treat this as unpatched and prioritize the workarounds below until a fix is released.
  • If no patch:
    • Restrict or disable public access to api/sat_proxy.php until a vendor fix is available.
    • Implement a strict allowlist of permitted destination hosts/schemes for the proxy functionality, rejecting requests to loopback, link-local (including cloud metadata addresses such as 169.254.169.254), and RFC1918 private address ranges.
    • Disable automatic redirect following in the proxy’s HTTP client to prevent redirect-based SSRF bypasses.
    • Deploy network-level egress controls (firewall/security groups) to prevent the application server from reaching internal management interfaces or cloud metadata services.
    • Monitor logs for anomalous outbound requests originating from the sat_proxy.php endpoint, particularly requests targeting internal IP ranges.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge