Categories
CVE-2026-107856 medium CVSS 4.5

CiviForm simplifies applications for government benefits programs by reusing applicant data across multiple benefit…

Summary

Vulnerability reported (CVE-2026-107856). Confidential information can be exposed externally. Exploitable via GET /admin/tiDash/editClientForm/.

Original description

The description as published by the source.

CiviForm simplifies applications for government benefits programs by reusing applicant data across multiple benefit applications. Prior to 3.33.0, GET /admin/tiDash/editClientForm/:accountId verifies that the requester is a Trusted Intermediary but showEditClientForm performs a raw lookupAccount(accountId) without confirming that the citizen account belongs to the requester's trustedIntermediaryGroup. An authenticated Trusted Intermediary can enumerate accountId values and read the applicant display name, including the citizen's name and email address, for accounts outside the intermediary's group. This issue is fixed in version 3.33.0.

Source: NIST National Vulnerability Database NVD

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-107856 has been found.
Attackers can target a specific entry point like GET /admin/tiDash/editClientForm/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 4.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-107856" on the vendor's site.

CVE-2026-107856 — CWE-639 / CVSS v3 4.5
Attack vector: remote (network-reachable)
Attack surface: GET /admin/tiDash/editClientForm/
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-639) has been reported. Attackers reach the vulnerable code path via GET /admin/tiDash/editClientForm/.

📍 Affected scope

Check the vendor advisory for the affected versions. Attack surface: GET /admin/tiDash/editClientForm/.

🔥 Severity

Severity: Medium (CVSS 4.5/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 /admin/tiDash/editClientForm/ 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・依存マニフェストで影響コンポーネントを特定する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'GET /admin/tiDash/editClientForm/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Post-deployment verification verify
    Replay attack against GET /admin/tiDash/editClientForm/ 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