# CVE-2026-111621: TDuck Survey Form through 5.3 Missing Authorization via /user/form/setting/{key}

> Authenticated users can read other owners' form settings, including passwords and emails, by accessing a specific endpoint with a public form key.

- **Severity:** Medium 5.3 (`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`)
- **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 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-7p6v-mhj8-c3pr

## What is CVE-2026-111621?

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

### Official description

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.

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

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


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

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

## Is CVE-2026-111621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111621 is a medium-severity missing authorization vulnerability in TDuckCloud tduck-survey-form, published on 16 Oct 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-111621 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-111621/ (Markdown: https://insights.sbomify.com/CVE-2026-111621/index.md)
```

## Sources

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

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