CVE-2026-61529: Endatix: Blind second-order SSRF via anonymous form-submission file URLs (`SubmissionFileExtractor`)
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-28).
Weakness: CWE-918: Server-Side Request Forgery (SSRF)
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality low, integrity none, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 4 references on Exploit Observer
Live scores
- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.986
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| endatix | version < 0.7.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-61529 Endatix - Stored Server-Side Request Forgery via Submission File URL. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-61529 Endatix - Stored Server-Side Request Forgery via Submission File URL"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/submissions"; nocase; fast_pattern; content:"/forms/"; nocase; http.request_body; content:"content"; nocase; pcre:"/\x22content\x22\s*\x3a\s*\x22https?\x3a\/\//i"; classtype:web-application-attack; reference:cve,CVE-2026-61529; reference:url,https://www.exploit.observer/?keyword=CVE-2026-61529&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=endatix&match=exact; sid:1103010; rev:1;)
CVE-2026-61529.rules on GitHub
References
Other references
- https://github.com/endatix/endatix/security/advisories/GHSA-jw28-j36r-gp9m (x_refsource_CONFIRM)
- https://github.com/endatix/endatix/pull/824 (x_refsource_MISC)
- https://github.com/endatix/endatix/commit/795b8aed71060f11da39971b9130130f5ef49362 (x_refsource_MISC)
- https://github.com/endatix/endatix/releases/tag/v0.7.0 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.