CVE-2026-92815 dgtlmoon CVE debrief

Who should care

Defenders responsible for changedetection.io instances, especially those exposed to untrusted networks, should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure, plan for updates or mitigations, and monitor for suspicious activity.

Why it matters

Defenders should prioritize verifying and remediating this SSRF vulnerability in changedetection.io instances, especially those exposed to untrusted networks, to prevent unauthorized access to internal addresses.

• Verify exposure of changedetection.io instances to untrusted networks
• Remediate vulnerable changedetection.io instances to prevent unauthorized access
• Monitor changedetection.io instances for suspicious activity

Technical summary

changedetection.io through 0.60.6 fails to validate the Goto URL action in browser steps, allowing unauthenticated attackers to access internal addresses by supplying arbitrary internal URLs in the optional_value parameter. This Server-Side Request Forgery (SSRF) vulnerability can lead to unauthorized access to internal addresses and potentially sensitive information. Defenders should prioritize verifying and remediating this vulnerability in changedetection.io instances, especially those exposed to untrusted networks.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in changedetection.io instances, especially those exposed to untrusted networks.

Recommended defensive actions

• Verify changedetection.io instances for exposure to untrusted networks
• Remediate vulnerable changedetection.io instances by updating to a fixed version
• Monitor changedetection.io instances for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but additional information on affected versions and remediation is limited. Further verification is needed to determine the full scope of affected systems and to confirm vendor guidance on updates or mitigations. Defenders should verify exposure of changedetection.io instances to untrusted networks and review compensating controls for exposed systems.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.