Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister/authenticate as any low-priv user
-
ExploitCopy 8-char form key from public fill link
-
ExecutionGET /user/form/setting/{key} without ownership check
-
ImpactHarvest write password, owner e-mail, WeChat openIds
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires (1) a valid authenticated account on the target TDuck Survey Form instance - any low-privileged user suffices (CVSS PR:L), so risk is elevated where self-service user registration is enabled - and (2) knowledge of the 8-character form key, which is not a secret because it is embedded in the public survey fill link shared with respondents. No user interaction from the victim and no special server configuration are needed; the flaw stems from the /user/form/setting/{key} endpoint omitting an owner/authorization check. Limiting factors: the attacker must authenticate first, and disclosure is confined to per-form settings (write password, owner notification e-mail, WeChat openIds) rather than whole-system data. |
| Impact | This is a genuine but modest-severity authorization flaw (CWE-639, IDOR), not a critical priority. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L) is internally consistent with the description: network-reachable, low-complexity, requires an authenticated low-privileged account, and yields limited confidentiality impact only. No EPSS score, no CISA KEV listing, and no POC/exploit-code flag were supplied in the input, so there is no public exploit identified at time of analysis - the signals are coherent rather than conflicting. The risk is bounded by the PR:L authentication requirement and by the fact that only per-form settings (write password, owner notification e-mail, WeChat openIds) are disclosed, not full application compromise or integrity/availability impact. Note: the leaked 'form write password' could enable downstream unauthorized form edits, so confidentiality impact is arguably more consequential than a raw C:L suggests, but this remains a targeted, authenticated data-disclosure issue rather than a mass-exploitable RCE. Treat as a real fix-worthy bug of moderate urgency, especially for multi-tenant TDuck deployments with open user registration. |
| Exploit ScenarioDerived | An attacker registers or already holds any low-privileged account on a TDuck Survey Form instance, then copies the 8-character form key visible in a victim's public survey fill link. They issue an authenticated GET /user/form/setting/{key} request and receive the target form's raw settings, exposing the form write password, the owner's notification e-mail, and associated WeChat openIds. No public exploit code was identified in the provided data, but the technique is trivial to reproduce given the low attack complexity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Missing authorization in TDuck Survey Form through 5.3 allows any authenticated, low-privileged user to read another form owner's raw settings by calling GET /user/form/setting/{key} with the 8-character form key embedded in a public survey fill link. The endpoint returns the form write password, the owner's notification e-mail address and associated WeChat openIds, which can be chained into form tampering and targeted phishing; a valid account is required (CVSS PR:L, so risk is higher where self-service registration is open), no user interaction is needed, and no public exploit identified at time of analysis. Severity is modest rather than critical because disclosure is confined to per-form settings and the attacker must authenticate first.
RemediationAI
Patch status per the input data: patch available from vendor, with an upstream fix commit at https://github.com/TDuckCloud/tduck-survey-form/commit/984efd69f51778e3d1a9ea0feb0f7c9aed266c18 - upstream fix available (PR/commit); released patched version not independently confirmed, so administrators should upgrade to the earliest vendor build that includes commit 984efd69 or later and confirm the authorization check is present before relying on it. Because that commit bundles unrelated changes (Hutool 5.8.16 → 5.8.43 and a new tduck-ai module), cherry-picking only the ownership check in UserFormSettingController is safer than a wholesale merge if you maintain a fork. Where an immediate upgrade is impossible, block or restrict external access to the /user/form/setting/{key} route at the reverse proxy/WAF so only trusted administrative networks can reach it (side effect: legitimate owners may lose access to settings screens from untrusted networks), and disable self-service/public user registration so attackers cannot obtain the low-privileged account the exploit requires (side effect: blocks legitimate new users). Treat the disclosed values as compromised: rotate the form write passwords, rotate or remove the exposed owner notification e-mail addresses and WeChat openIds from form configuration, and reissue the 8-character form keys so previously shared public fill links no longer map to the same records (side effect: existing distributed links stop working and must be redistributed). Cross-check the vendor advisory at https://www.vulncheck.com/advisories/tduck-survey-form-through-5.3-missing-authorization-via-user-form-setting-key and the technical writeup at https://hackmd.io/@hieuPenguinnn/tduck-survey-form-setting-cross-user-disclosure for any updated fixed version.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-639 (Authorization Bypass Through User-Controlled Key), a classic IDOR in the Spring Boot backend of TDuck Survey Form, an open-source Java survey/form platform published by TDuckCloud. The controller at tduck-api/src/main/java/com/tduck/cloud/api/web/controller/UserFormSettingController.java (lines 66-75) takes the form identifier as a path variable {key} and returns the matching form-setting record without verifying that the caller owns or is authorized for that form; the code simply trusts the caller-supplied key. Because the same 8-character key is embedded in the public fill link shared with respondents, it is not a secret and is trivially obtainable by anyone who can see or receive a link. The CPE cpe:2.3:a:tduckcloud:tduck-survey-form:*:*:*:*:*:*:*:* marks the affected TDuckCloud product line, and the upstream remediation commit (984efd69f51778e3d1a9ea0feb0f7c9aed266c18) also bumps the Hutool library from 5.8.16 to 5.8.43 and introduces a new tduck-ai module, indicating the fix landed in a broader development branch rather than a narrow patch. Given the assessed vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, impact is limited to confidentiality of per-form configuration (write password, owner notification e-mail, WeChat openIds) rather than whole-system data, and the primary risk is credential/social-engineering chaining rather than direct server compromise.
Know when Tduck Survey Form gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Network endpoint reachable with low complexity using a public form key, but an authenticated account is required (PR:L); impact is limited confidentiality disclosure of form settings only, no integrity or availability effect.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
TDuck Survey Form through 5.3 contains a missing authorization vulnerability that allows any authenticated user to read other owners' raw form settings via GET /user/form/setting/{key}. Attackers can supply the 8-character form key from a public fill link to obtain the form write password, owner notification e-mail, and WeChat openIds.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Tduck Survey Form
View allMissing server-side enforcement of the write/submission password in TDuck survey form through 6.0 allows remote unauthen
TDuck Survey Form 6.0 fails open in its form-ownership authorization check, letting an authenticated user read submissio
Authenticated non-admin users can add, modify, or delete global form themes and theme categories in TDuck Survey Form th
Authenticated users who know a form's key can flood TDuck Survey Form through 6.0 with unlimited submissions via POST /u
This is a genuine but bounded-priority integrity flaw: in TDuck Survey Form through version 5.0, any authenticated low-p
Authenticated users of TDuck Survey Form through version 5.3 can hijack forms they do not own and redirect their submiss
EUVD-2026-103043
GHSA-7p6v-mhj8-c3pr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB