Squidex
CVE-2026-24736
CRITICAL
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as high-privilege user
-
DeliveryConfigure webhook with localhost URL
-
ExploitTrigger rule execution
-
ExecutionBackend sends HTTP request to internal service
-
ImpactAccess internal resources or execute commands
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | High-privilege user account required. Squidex Rules engine with webhook action support enabled. No URL validation restricting localhost/127.0.0.1 addresses in webhook configuration. Rule triggering capability accessible (manual endpoint or content update). Internal services listening on localhost without additional authentication. |
| Impact | CVSS 9.1 with high-privilege requirement (admin). PoC available. Impact is amplified in cloud environments where internal metadata services (169.254.169.254) may expose credentials. |
| Exploit ScenarioDerived | Compromised or malicious admin configures webhook pointing to cloud metadata endpoint, triggers rule execution, retrieves IAM credentials or internal service data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 12, 2026
Server-Side Request Forgery (SSRF) vulnerability in Squidex CMS webhook configuration allows authenticated administrators to make requests to internal services by specifying localhost or internal IP addresses as webhook destinations. PoC available.
Earlier versions of this analysis (1)
SSRF via webhook URL parameter in Squidex headless CMS.
RemediationAI
Update Squidex beyond 7.21.0. Implement network-level egress filtering to block requests to internal/metadata addresses from the CMS.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-918 in Squidex up to v7.21.0. The webhook URL parameter accepts local addresses (127.0.0.1, localhost) without validation, enabling internal network scanning and service access when rules are triggered.
Know when Squidex gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
Squidex is an open source headless content management system and content management hub. Versions of the application up to and including 7.21.0 allow users to define "Webhooks" as actions within the Rules engine. The url parameter in the webhook configuration does not appear to validate or restrict destination IP addresses. It accepts local addresses such as 127.0.0.1 or localhost. When a rule is triggered (Either manual trigger by manually calling the trigger endpoint or by a content update or any other triggers), the backend server executes an HTTP request to the user-supplied URL. Crucially, the server logs the full HTTP response in the rule execution log (lastDump field), which is accessible via the API. Which turns a "Blind" SSRF into a "Full Read" SSRF. As of time of publication, no patched versions are available.
Executive ViewAI
Squidex versions up to 7.21.0 contain a critical vulnerability (CVSS 9.1) in the Rules engine's webhook functionality that could allow attackers to execute arbitrary actions or compromise system integrity. Organizations running affected versions face immediate risk of unauthorized data access, system manipulation, or service disruption, particularly if Squidex is used to manage business-critical content.
Disable webhook functionality in Rules engine until patch is available; implement Web Application Firewall (WAF) rules to block suspicious Rules engine requests; restrict Squidex network access via firewall to trusted internal networks only; enforce strict authentication/authorization controls on Rules engine access; implement real-time monitoring and alerting on webhook creation/modification events; consider isolating affected Squidex instances to prevent lateral movement if compromised.
Threat Intelligence Overview
NVD
CVE.org
EPSS
GitHub
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Affected Products (CPE)GitHub Advisory
Squidex is an open source headless CMS and content management hub. Rated high severity (CVSS 7.2), this vulnerability is
Cross-Site Request Forgery (CSRF) in GitHub repository squidex/squidex prior to 7.4.0. Rated medium severity (CVSS 6.5),
Squidex is an open source headless CMS and content management hub. Rated medium severity (CVSS 6.1), this vulnerability
Squidex before 7.4.0 was discovered to contain a squid.svg cross-site scripting (XSS) vulnerability. Rated medium severi
Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0. Rated medium severi
Squidex before 7.9.0 allows XSS via an SVG document to the Upload Assets feature. Rated medium severity (CVSS 5.4), this
Squidex is an open source headless CMS and content management hub. Rated medium severity (CVSS 5.4), this vulnerability
Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0. Rated medium severi
Server-Side Request Forgery in Squidex versions prior to 7.23.0 allows authenticated users with asset upload permissions
Server-Side Request Forgery (SSRF) in Squidex versions before 7.23.0 allows authenticated users with schema editing perm
Server-Side Request Forgery in Squidex's backup restoration endpoint allows authenticated administrators to probe intern
Blind Server-Side Request Forgery (SSRF) in Squidex prior to version 7.23.0 allows authenticated administrators to force
Exploit-DB