Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-100305 Overview
CVE-2026-100305 is a missing authorization vulnerability [CWE-862] in TDuck survey form through version 6.0. The authenticated submission endpoint POST /user/form/data/create fails to enforce form fill-in restrictions. Authenticated attackers who know a form's key can submit unlimited entries to any form on the platform. The bypass circumvents publish status checks, time window enforcement, submission quotas, and per-IP rate limits. Attackers can use this flaw to falsify collected survey results and poll data at scale.
Critical Impact
Authenticated users can flood any TDuck survey with arbitrary submissions, bypassing all server-side fill-in restrictions and compromising the integrity of collected form data.
Affected Products
- TDuck survey form through version 6.0
- tduck-api component (UserFormResultController)
- tduck-form component (UserFormSettingServiceImpl)
Discovery Timeline
- 2026-09-25 - CVE-2026-100305 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-100305
Vulnerability Analysis
The flaw resides in the authenticated form submission flow of the TDuck survey platform. The controller method handling POST /user/form/data/create accepts submissions from any authenticated user who supplies a valid form key. The server does not evaluate the fill-in restrictions defined for the target form before persisting the submission. As a result, protections configured by form owners — publish state, open/close time windows, maximum entry quotas, and per-IP submission caps — are silently ignored on this endpoint.
The impact is limited to integrity of collected results. Attackers cannot read other users' responses or modify system configuration through this issue, but they can poison datasets used for decision-making, voting, or research. For technical details, see the VulnCheck Advisory for TDuck Survey Form.
Root Cause
The root cause is missing authorization logic [CWE-862] in the submission handler. The UserFormResultController persists results without invoking the restriction checks implemented in UserFormSettingServiceImpl. The responsibility for enforcing form settings was placed on the public submission path only, leaving the authenticated endpoint unguarded. See the UserFormResultController source and the UserFormSettingServiceImpl source for the divergent code paths.
Attack Vector
An attacker with a low-privilege authenticated account on the TDuck instance sends crafted HTTP POST requests to /user/form/data/create. Each request includes a known form key and a JSON body representing a submission. The server accepts and stores every request regardless of the target form's state. A public proof-of-concept script is available in the GitHub PoC Script for CVE.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-100305
Indicators of Compromise
- High-volume POST /user/form/data/create requests originating from a single authenticated session or IP address.
- Submissions recorded against forms that are unpublished, closed, or past their configured time window.
- Submission counts for a form exceeding the configured quota or per-IP limit stored in form settings.
Detection Strategies
- Correlate application logs with form configuration data to flag submissions that violate publish status, time window, or quota rules.
- Baseline normal submission rates per form and alert on sudden spikes from authenticated accounts.
- Monitor web access logs for repetitive requests to /user/form/data/create carrying the same form key.
Monitoring Recommendations
- Enable detailed audit logging on the UserFormResultController endpoints and retain logs for retrospective review.
- Forward TDuck application and web server logs to a centralized analytics platform for behavioral analysis.
- Alert security operations when a single account submits to multiple distinct form keys within a short time window.
How to Mitigate CVE-2026-100305
Immediate Actions Required
- Restrict network access to the TDuck administrative and authenticated endpoints to trusted users and networks only.
- Audit existing form result datasets for anomalous submission patterns and purge entries identified as fraudulent.
- Rotate or restrict form keys and tighten account provisioning to limit the pool of authenticated attackers.
Patch Information
No vendor patch is referenced in the NVD advisory at publication. Monitor the TDuck Survey Form repository for a release that adds restriction enforcement to UserFormResultController before persisting results. Review the VulnCheck Advisory for TDuck Survey Form for remediation updates.
Workarounds
- Place a reverse proxy or Web Application Firewall rule in front of /user/form/data/create to enforce per-user and per-IP rate limits.
- Deploy a server-side middleware or filter that re-evaluates form publish state, time window, and quota before the controller executes.
- Disable new account registration on public TDuck instances to reduce the attacker pool able to reach the authenticated endpoint.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

