CVE-2026-24754
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 stored XSS vulnerability in Kiteworks Secure Data Forms could allow an authenticated attacker to execute arbitrary JavaScript code in other users' sessions. 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 confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in Kiteworks Secure Data Forms that allows authenticated attackers to embed malicious JavaScript code into form data. When other users view or interact with the compromised form data, the malicious script executes in their session, potentially enabling session hijacking, data theft, or actions on behalf of victims.
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
- 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 installationLocate the Kiteworks application server and confirm Accellion Kiteworks is deployed. Check server inventory, container images, or documentation for Kiteworks instances.Affected if Kiteworks is present in the environment
-
Determine installed Kiteworks versionAccess the Kiteworks admin console or check system files for the version number. Typical locations: About page in admin UI, version file in installation directory, or API endpoint /api/version.Affected if Version is lower than 9.3.0 (e.g., 9.2.x, 9.1.x, earlier versions)
-
Check Secure Data Forms module statusIn the Kiteworks admin console, navigate to the Secure Data Forms configuration area or check if forms have been created. Look for any enabled form templates or active form instances.Affected if Secure Data Forms module is enabled or forms exist in the system
-
Inspect form field configurationsReview the form field settings in Secure Data Forms, particularly any custom or third-party field types. Check if input validation or content type restrictions are configured.Affected if Forms accept rich content or custom HTML in data fields and no output encoding is visible
The environment is affected if Kiteworks version is below 9.3.0 AND Secure Data Forms are in use, as the stored XSS can be triggered when users view form data.
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 patch for this vulnerability. Until upgrade is complete, consider restricting access to Secure Data Forms to only highly trusted users and monitoring for suspicious form submissions.
9.3.0
- Upgrade Kiteworks to version 9.3.0 or later to remediate the stored XSS vulnerability in Secure Data Forms
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24754 — 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-24754 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