CVE-2026-23636
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). In Kiteworks Secure Data Forms prior to version 9.2.1, the manager of a form could potentially exploit an Unrestricted Upload of File with Dangerous Type due to a missing validation. Upgrade Kiteworks to version 9.2.1 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 · moderate confidenceKiteworks Secure Data Forms prior to version 9.2.1 contains an Unrestricted Upload of File with Dangerous Type vulnerability due to missing file validation. An authenticated user with form manager privileges can upload files with dangerous extensions or content, potentially leading to remote code execution if those files are served by the web server.
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.2.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Kiteworks installationLocate the Kiteworks installation directory or check running services for Accellion Kiteworks componentsAffected if Kiteworks is present and the Secure Data Forms module is in use
-
Determine installed Kiteworks versionAccess the Kiteworks admin interface or check the version file in the installation directoryAffected if The installed version is below 9.2.1
-
Verify Secure Data Forms module is activeCheck the Kiteworks admin panel for enabled modules, specifically the Secure Data Forms functionalityAffected if Secure Data Forms is enabled and accessible to users
-
Identify form manager role assignmentsReview user roles in the Kiteworks admin panel to determine which users have form manager privilegesAffected if Any user accounts are assigned form manager privileges
-
Inspect file upload configuration in Secure Data FormsExamine the file upload settings within the Secure Data Forms module for allowed file typesAffected if File type validation is missing or overly permissive for uploaded files
A user is affected if running Kiteworks version below 9.2.1 with Secure Data Forms enabled and users have form manager privileges, particularly if file upload restrictions are not enforced.
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.2.1
Upgrade Kiteworks to version 9.2.1 or later to receive the patch that adds proper file type validation in Secure Data Forms.
9.2.1 or later
- Backup the current Kiteworks installation and all associated data before proceeding with the upgrade
- Obtain Kiteworks version 9.2.1 or later from the official Kiteworks vendor distribution channels
- Consult the official Kiteworks upgrade documentation for your current version
- Execute the upgrade procedure following the vendor's recommended steps
- After completing the upgrade, verify that Secure Data Forms are functioning correctly
- Confirm that file upload validation is now properly enforced in Secure Data Forms
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23636 — 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-23636 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