Kiteworks Secure Data Forms SQL injection

Answer in brief

CVE-2026-102109 records a High severity (CVSS 7.1) vulnerability in Kiteworks Secure Data Forms SQL injection. The current sources do not mark it as known exploited. The current feed maps Kiteworks/Secure Data Forms (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 30, 2026Updated Sep 30, 2026Source checked Sep 30, 2026First seen by HOL Sep 30, 2026Material review Sep 30, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Kiteworks/Secure Data Forms (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Kiteworks/Secure Data Formsgeneric	>=0 <9.5.1	9.5.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for Kiteworks/Secure Data Forms.
Review the reported fix. Update Kiteworks/Secure Data Forms to 9.5.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 30, 2026

Sources and claim methodology

Upstream source description

A SQL injection vulnerability existed in Kiteworks Secure Data Forms, where a value derived from the authenticated user's stored account data was incorporated into a database query without proper sanitization. An authenticated user could potentially influence that value to inject SQL. Exploitation requires an authenticated session and applies only to deployments where a specific optional feature is in use.

Quoted source text, attributed separately from HOL analysis.