CVE-2026-24750
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, an authenticated attacker could exploit an Improper Neutralization of Input During Web Page Generation as Stored XSS when modifying forms. 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 · high confidenceKiteworks Secure Data Forms prior to version 9.2.1 contains a stored cross-site scripting (XSS) vulnerability where authenticated attackers can inject malicious JavaScript code through form modification fields. The injected payload persists and executes when other users view the affected forms.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 and versionLocate the Kiteworks application and retrieve its installed version number through the administrative interface or system inventoryAffected if The installed version is Accellion Kiteworks prior to 9.2.1
-
Verify Secure Data Forms module is activeCheck if the Secure Data Forms feature is enabled in the Kiteworks administrative console under module or feature settingsAffected if Secure Data Forms is enabled and the Kiteworks version is below 9.2.1
-
Review form definitions for injected scriptsAccess the form creation or modification interface in Secure Data Forms and inspect any existing form field definitions for unexpected script tags, event handlers, or javascript: URIsAffected if Any form contains user-defined HTML, script tags, or JavaScript event handlers in field labels, descriptions, or default values
-
Audit recent form modificationsReview form modification logs or audit trails to identify any recent changes made by users that introduced unusual content into form fieldsAffected if Form modifications contain base64-encoded strings, eval() calls, or suspicious character sequences typical of obfuscated XSS payloads
A Kiteworks installation is affected if it runs Secure Data Forms on a version below 9.2.1 and contains forms with unsanitized script content injected into modification fields.
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 apply the patch that properly sanitizes user input in form fields.
9.2.1 or later
- Confirm current Kiteworks version is below 9.2.1 by checking the administration interface or version documentation
- Plan upgrade during a maintenance window following standard backup procedures
- Obtain Kiteworks version 9.2.1 or later from official channels
- Execute upgrade following Kiteworks upgrade documentation or contact vendor support for assisted upgrade
- Verify upgrade completed successfully and the version is now 9.2.1 or later
- Test that the Secure Data Forms functionality works correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24750 — 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-24750 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