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

New CVE Detected

CVE-2026-92815 – Server-Side Request Forgery (SSRF) – changedetection.io ≤ 0.60.6

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

Summary

CVE-2026-92815 is a server-side request forgery (SSRF) vulnerability in changedetection.io, an open-source website change monitoring tool, affecting all versions through 0.60.6. The flaw lies in the "Goto URL" browser-step action, which fails to validate the destination address before navigating, letting an unauthenticated attacker force the application server to issue requests to internal or restricted network locations. The issue is rated HIGH severity.

Technical details

  • Root cause: The action_goto_url function in browser_steps.py passes the browser step’s optional_value parameter directly to the underlying browser automation page.goto() call with no validation of the target address.
  • Trigger conditions: A user (including an unauthenticated attacker, per the CVE description) configures or submits a watch containing a "Goto URL" browser step whose target is an internal or restricted address (e.g., loopback, link-local, or private RFC1918 ranges, or cloud metadata endpoints).
  • Attack vector: Network — no authentication or user interaction beyond submitting the crafted browser step is required.
  • Impact: The application server can be coerced into fetching content from internal-only services, enabling network reconnaissance and disclosure of internal HTTP responses (e.g., internal APIs, admin panels, or cloud instance metadata). The scored impact is limited to confidentiality; integrity and availability are not affected.

Affected software

  • changedetection.io versions 0 through 0.60.6 (all releases up to and including 0.60.6)

Severity

  • CVSS v4.0 Base Score: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1 Base Score: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: As of this writing, no vendor-confirmed patched release for this specific browser-step SSRF issue has been identified. Monitor the official changedetection.io GitHub repository and release notes for a fix and upgrade as soon as one is published.
  • If no patch is available:
    • Restrict or disable use of the "Goto URL" browser step feature where not strictly required.
    • Apply egress filtering on the host running changedetection.io so it cannot reach internal-only networks, loopback addresses, link-local ranges, or cloud metadata services (e.g., 169.254.169.254).
    • Place changedetection.io behind authentication and avoid exposing its interface directly to the internet.
    • Segment the host running changedetection.io away from sensitive internal services using firewall rules or network ACLs.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge