Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-100304 medium CVSS 5.3

Vulnerability in TDuck survey form (CVE-2026-100304)

Summary

Vulnerability in TDuck survey form (CVE-2026-100304). Confidential information can be exposed externally. Exploitable via GET /user/form/data/details.

Original description

The description as published by the source.

TDuck survey form 6.0 contains an information disclosure vulnerability in FormAuthUtils.hasPermission that fails open when a form does not exist, allowing authenticated users to access deleted form submissions. Attackers can read orphaned submission data including personal information by providing a known dataId to the GET /user/form/data/details endpoint after the form has been permanently deleted.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-100304 has been found in TDuck survey form.
Attackers can target a specific entry point like GET /user/form/data/details over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "TDuck survey form CVE-2026-100304" on the vendor's site.

CVE-2026-100304 (TDuck survey form) — CWE-636 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /user/form/data/details
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-636) exists in TDuck survey form. Attackers reach the vulnerable code path via GET /user/form/data/details.

📍 Affected scope

Check the vendor advisory for the affected versions of TDuck survey form. Attack surface: GET /user/form/data/details.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /user/form/data/details requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで TDuck survey form を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /user/form/data/details' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /user/form/data/details への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against GET /user/form/data/details on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details