CVE-2026-23638
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, an Insecure Direct Object Reference (IDOR) vulnerability in Kiteworks Secure Data Forms allows an authenticated attacker to tamper with the internal approval flow configurations of forms belonging to other users due to insufficient authorization checks on resource ownership. 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 confidenceAn Insecure Direct Object Reference (IDOR) vulnerability in Kiteworks Secure Data Forms allows authenticated attackers to modify approval flow configurations of forms owned by other users due to insufficient authorization checks on resource ownership.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 installed Kiteworks versionAccess the Kiteworks admin console or check the version file (typically /opt/kiteworks/version or via admin UI: Settings > System > About)Affected if Version is below 9.3.0
-
Verify Secure Data Forms is accessibleConfirm the Secure Data Forms feature is enabled and accessible in the Kiteworks deploymentAffected if Forms module is active and version is below 9.3.0
-
Review audit logs for form configuration changesExamine Kiteworks audit logs (typically in admin UI: Reports > Audit Logs or log files) for events related to form_approval_flow modifications, specifically looking for user IDs modifying forms they do not ownAffected if Logs show form configuration modifications by users other than form owners
If Kiteworks version is below 9.3.0 and Secure Data Forms is in use, the environment is vulnerable to unauthorized form configuration modifications
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 apply the vendor patch that adds proper authorization validation for form ownership.
9.3.0 or later
- 1. Back up the current Kiteworks installation and database before starting the upgrade process.
- 2. Download Kiteworks version 9.3.0 or later from the official Kiteworks distribution channel.
- 3. Apply the upgrade following Kiteworks standard upgrade procedures (consult official documentation for your deployment method).
- 4. Verify the upgrade was successful by checking the Kiteworks version and confirming the Secure Data Forms functionality is working correctly.
- 5. Test that authorization checks are now properly enforced on Secure Data Forms approval flow configurations.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23638 — 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-23638 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