CVE Catalog

CVE-2026-61529

MediumCVSS 4.7
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.21%

11th percentile - higher than 11% of all known CVEs

Summary

In Endatix before 0.7.0, the anonymous POST /forms/{formId}/submissions endpoint stores attacker-controlled JsonData that may contain a file object with an HTTP/HTTPS URL. When a staff member with submissions.view permission triggers file retrieval, the server performs a GET request without validating the destination URL, enabling second-order SSRF to internal services, cloud metadata, and loopback addresses.

Risk Assessment

An attacker can force the server to make requests to internal resources, risking exposure of infrastructure data or abuse of network trust; disclosure is indirect since the response is placed in the staff viewer's ZIP.

Recommendation

Update Endatix to version 0.7.0 or later. Restrict outbound network traffic from the application server and consider validating URLs in JsonData at the application layer.

Related vulnerabilities

Original NVD description (English source)

Endatix is a self-hosted form and survey management platform with a headless API. Prior to 0.7.0, the anonymous `POST /forms/{formId}/submissions` endpoint stores attacker-controlled `JsonData` after checking only that the JSON is well formed. A file object with `name`, `type` and `content` fields can contain an HTTP or HTTPS URL. When a staff member with `submissions.view` permission invokes `POST /forms/{formId}/submissions/{submissionId}/files`, `GetFilesHandler` passes the stored data to `SubmissionFileExtractor` in `src/Endatix.Infrastructure/Features/Submissions/SubmissionFileExtractor.cs`, which calls `HttpClient.GetAsync` without validating the destination URL, host or resolved IP addresses against internal address ranges. This permits stored, second-order server-side GET requests to internal services, cloud metadata, loopback and link-local addresses from the server's network position. The form must have `IsPublic` and `IsEnabled` set, and an anonymous submission must pass reCAPTCHA v3 when configured. The fetched response is placed in the staff viewer's ZIP, not returned directly to the attacker, so disclosure to the attacker is blind or indirect through observable request behavior or information exposed by the viewer. No integrity or availability impact is asserted; data: and raw-base64 `content` are decoded locally without network requests. This issue is fixed in version 0.7.0.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS