# CVE-2026-92567: TDuck survey form through 5.0 Unauthorized Data Modification

> Authenticated users can modify other users' survey responses due to missing ownership validation in the update endpoint.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-cxpf-jm7w-39v7

## What is CVE-2026-92567?

CVE-2026-92567 is a high-severity missing authorization vulnerability in TDuckCloud tduck-survey-form, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TDuck survey form through version 5.0 contains an authorization bypass vulnerability in the POST /user/form/data/update endpoint that allows authenticated users to overwrite other users' form submission data. Attackers can discover submission identifiers allocated in narrow ranges and modify arbitrary form responses containing personal data by sending update requests without ownership validation.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-92567?


## How do I fix CVE-2026-92567?

No fix has been published for CVE-2026-92567 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92567 being exploited?

There is no known exploitation of CVE-2026-92567 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92567 and fix it if it is affected.

What it is: CVE-2026-92567 is a high-severity missing authorization vulnerability in TDuckCloud tduck-survey-form, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92567 in the wild and no public exploit code.

Affected product: TDuckCloud tduck-survey-form. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92567/ (Markdown: https://insights.sbomify.com/CVE-2026-92567/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92567
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92567
- OSV: https://osv.dev/vulnerability/CVE-2026-92567

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92567/
Summaries are generated and may contain mistakes; the official description above is the record.