Authenticated form-response overwrite via missing ownership validation
Published Sep 16, 2026 · Updated Sep 17, 2026
Authorization bypass in TDuckCloud tduck-survey-form 5.0 and earlier allows remote authenticated users to overwrite other users' submissions. The POST /user/form/data/update handler accepts a caller-supplied submission identifier and updates the record without verifying that the authenticated account owns the targeted response. Any authenticated account can enumerate narrowly allocated identifiers and replace arbitrary response content, including stored personal data.
Summary
What happened
Authorization bypass in TDuckCloud tduck-survey-form 5.0 and earlier allows remote authenticated users to overwrite other users' submissions. The POST /user/form/data/update handler accepts a caller-supplied submission identifier and updates the record without verifying that the authenticated account owns the targeted response. Any authenticated account can enumerate narrowly allocated identifiers and replace arbitrary response content, including stored personal data.
The record
- CVE
- CVE-2026-92567
- Published
- Sep 16, 2026
- Updated
- Sep 17, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started