Security readout for executives and security teams
Plain-English summary
Squidex versions up to 7.21.0 let privileged users configure webhooks that the server will call without restricting internal destinations. This can make Squidex fetch local or internal services and expose the full response in rule logs. For organizations running Squidex, this creates a serious risk of internal data exposure and possible impact to connected systems.
Executive priority
Treat as urgent for any production Squidex deployment, especially where privileged access is broadly assigned or the service can reach sensitive internal systems. Prioritize access restriction, egress control, and vendor guidance while monitoring for an official fix.
Technical view
CVE-2026-24736 is an SSRF in Squidex webhook rules. The webhook URL accepts destinations such as localhost or 127.0.0.1. When triggered, the backend performs the request and stores the full HTTP response in the rule execution log lastDump, making the issue a full-read SSRF. Affected versions are Squidex through 7.21.0. CVSS is 9.1.
Likely exposure
Exposure is limited to Squidex deployments where users with sufficient privileges can create or modify rule webhooks. The CVSS vector lists privileges required as high, but no user interaction is needed after access. Internet-facing Squidex instances may increase business risk if privileged accounts are compromised.
Exploitation context
The advisory describes exploitation through configured webhooks triggered manually or by content/rule events. The provided sources do not report active exploitation, and the CVE is not marked KEV. As of publication, the source bundle states no patched versions were available.
Researcher notes
Evidence comes from the CVE record and GitHub advisory. The issue requires high privileges but has scope change and high confidentiality, integrity, and availability impact. No public exploit status or patch is confirmed in the provided sources. Avoid assuming affected hosted services or downstream distributions without vendor confirmation.
Mitigation direction
- Identify all Squidex deployments and versions through 7.21.0.
- Restrict who can create or modify webhook rules.
- Review webhook destinations for localhost, loopback, link-local, or internal addresses.
- Limit Squidex server egress to approved external webhook destinations.
- Monitor rule execution logs for unexpected response dumps.
- Check the Squidex advisory for patched versions or official mitigations.
Validation and detection
- Confirm whether Squidex version is 7.21.0 or earlier.
- Inventory tenants, apps, and rules using webhook actions.
- Review rule execution logs for internal service responses in lastDump.
- Check audit logs for recent webhook configuration changes.
- Verify network controls prevent Squidex from reaching internal metadata or admin services.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24736 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Squidex/squidex/security/advisories/GHSA-wxg2-953m-fg2wCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.