Squidex has Server-Side Request Forgery (SSRF) Issue in Webhook Configuration
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Squidex | squidex | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Squidex.io | Squidex | — |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.489% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:squidex.io:squidex:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Squidex.io
Squidex.io squidex |
|
| Vendors & Products |
Squidex.io
Squidex.io squidex |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Squidex has Server-Side Request Forgery (SSRF) Issue in Webhook Configuration | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|