# CVE-2026-100303: TDuck survey form through 6.0 Missing Authorization in Form Theme Management Endpoints

> Authenticated non-admin users can modify or delete global form themes and categories, affecting other users' forms.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/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:** 25 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-47j6-wrmm-xx5g

## What is CVE-2026-100303?

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

### Official description

TDuck survey form through 6.0 lacks authorization checks on FormThemeController write endpoints for global form themes and categories. Authenticated non-admin users can add, modify, or delete themes and theme categories affecting forms owned by other users.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-100303 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100303 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100303 is a medium-severity missing authorization vulnerability in TDuckCloud tduck-survey-form, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100303 exists.

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-100303/ (Markdown: https://insights.sbomify.com/CVE-2026-100303/index.md)
```

## Sources

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

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