CVE-2026-24752
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKiteworks is a private data network (PDN). Prior to version 9.3.0, a reflected XSS vulnerability in Kiteworks Secure Data Forms could allow an external attacker to trick a user into executing arbitrary JavaScript code. Upgrade Kiteworks to version 9.3.0 or later to receive a patch.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a reflected Cross-Site Scripting (XSS) vulnerability in Kiteworks Secure Data Forms. The vulnerability allows an external attacker to inject malicious JavaScript code through unsanitized input (likely URL parameters) that gets reflected back to the user. When a victim clicks a crafted link, the attacker's JavaScript executes in their browser within the context of the Kiteworks application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Kiteworks installation versionAccess the Kiteworks admin console or system information page to determine the currently installed version number. This is typically found in the About or System Status section of the administrative interface.Affected if The installed version is below 9.3.0 (for example, 9.2.x, 9.1.x, or earlier releases).
-
Confirm Secure Data Forms component is activeVerify that the Secure Data Forms feature is enabled and accessible in the Kiteworks environment. Check the component status through the admin dashboard or by confirming the forms endpoint is reachable.Affected if Secure Data Forms is enabled and the version is below 9.3.0.
-
Inspect HTTP response for unsanitized input reflectionSubmit a test request to the Secure Data Forms endpoint with a benign test payload in a URL parameter (such as <script>alert(1)</script> or similar XSS probe). Examine the HTTP response to see if the input is reflected without proper encoding.Affected if The submitted payload is reflected verbatim in the response without HTML encoding, indicating the vulnerability is present.
-
Review access logs for malicious URL patternsExamine web server or proxy access logs for the Secure Data Forms endpoint, looking for unusual URL parameters that may indicate exploitation attempts or suspicious crafted links.Affected if Log entries show unexpected parameters or known XSS probe patterns targeting the forms endpoint.
You are affected if Kiteworks version is below 9.3.0 and the Secure Data Forms component is enabled, with unsanitized input reflected in HTTP responses.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.3.0
Upgrade Kiteworks to version 9.3.0 or later to receive the patch. This is a straightforward version upgrade that addresses the input sanitization issue in Secure Data Forms.
9.3.0 or later
- Verify current Kiteworks version by checking the admin dashboard or system information
- Download Kiteworks version 9.3.0 or later from the official Kiteworks distribution channel
- Review Kiteworks upgrade documentation for your specific deployment type
- Perform a full backup of the Kiteworks database and configuration files
- Execute the upgrade procedure following Kiteworks official upgrade instructions
- Verify the upgrade was successful by checking the version number
- Test the Secure Data Forms functionality to confirm the XSS vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24752 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data