Critical · published January 27, 2026
🚨 A misconfigured webhook in Squidex can turn your server into a data-leaking machine! 🔥 Just feed it a URL, and it'll pull in sensitive information without breaking a sweat! Think of it like a delivery service that takes any address and delivers packages without checking if it even exists — your server just sends out sensitive info as if it’s mail on an open street! 📦 An attacker could exploit this vulnerability to access sensitive information from internal systems, delivering full HTTP responses to a malicious URL. This could lead to an absolute treasure trove of data leakage, giving the attacker insight into internal processes and data you thought was secure.
Think of it like a delivery service that takes any address and delivers packages without checking if it even exists — your server just sends out sensitive info as if it’s mail on an open street! 📦 This vulnerability allows unauthorized HTTP requests through a lack of validation on the URL parameter in webhook configurations. When rules are triggered in Squidex, it sends requests to any destination IP, including local ones, thus transforming a blind SSRF vulnerability into a full read SSRF.
An attacker could exploit this vulnerability to access sensitive information from internal systems, delivering full HTTP responses to a malicious URL. This could lead to an absolute treasure trove of data leakage, giving the attacker insight into internal processes and data you thought was secure. To mitigate this, restrict the URL parameter in webhook configurations to only allow trusted addresses. Monitor your logs for any suspicious activity and prepare for future patches that may resolve this issue in upcoming versions of Squidex. You've got this! Stay vigilant and implement these protective measures! 🛡️