TDuck Survey Form (<= 6.0) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/tduck-survey-form--6.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 12 Oct 2026 13:43:15 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgIDOR Vulnerability in TDuck Survey Formhttps://feed.craftedsignal.io/briefs/2026-10-tduck-idor/Mon, 12 Oct 2026 13:43:15 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-tduck-idor/TDuck survey form through 6.0 contains an insecure direct object reference vulnerability that allows authenticated users to delete other users' form submissions by supplying arbitrary submission identifiers.TDuck survey form, through version 6.0, contains an insecure direct object reference (IDOR) vulnerability (CVE-2026-109164) that enables authenticated users to perform unauthorized deletions of form submissions. By manipulating the submission identifier within requests, an attacker can target and remove data belonging to other users across the platform. The vulnerability exists due to a lack of sufficient access control checks when processing submission deletion requests, allowing an attacker to iterate through sequential identifiers. This flaw poses a significant risk to data integrity and availability, as attackers can perform platform-wide data destruction. Organizations utilizing TDuck survey form should verify current versions and restrict access to the affected submission deletion functionality.

Impact

Successful exploitation of this vulnerability results in unauthorized data loss, where an attacker can delete arbitrary form submissions regardless of ownership. This impacts data integrity and historical record availability for organizations using the platform for surveys or data collection. The platform-wide scope of this flaw allows for mass deletion, potentially affecting the entire database of submissions.

Recommendation

  1. Upgrade to a version of TDuck survey form that addresses the IDOR vulnerability in the submission deletion logic.
  2. Implement request monitoring to detect high volumes of deletion requests originating from a single authenticated user session.
  3. Review access logs to identify anomalous deletion patterns, specifically those involving sequential numeric IDs.
  4. Restrict access to the submission management portal to trusted, authorized administrators only until the vulnerability is patched.
]]>highadvisoryweb-applicationidordata-lossimpact