CVE-2022-24110
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 MFT 7.5 may allow an unauthorized user to reset other users' passwords. This is fixed in version 7.6 and later.
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 MFT version 7.5 contains an authorization flaw that allows an unauthenticated or unauthorized user to reset passwords for other user accounts, potentially leading to unauthorized account takeover.
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< 7.6CVSS 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.
-
Determine installed Kiteworks MFT versionAccess the admin interface or check system files/binaries for the exact version number of Accellion Managed File Transfer/Kiteworks MFTAffected if The installed version is 7.5 or any version prior to 7.6 (e.g., 7.4, 7.3, etc.)
-
Confirm web interface accessibilityVerify that the Kiteworks MFT web portal is accessible from the networkAffected if The web interface is exposed without additional authentication barriers protecting the password reset function
-
Identify password reset endpoint exposureLocate the password reset or account recovery page within the Kiteworks MFT web applicationAffected if The password reset endpoint is reachable without prior authentication and accepts user account identifiers as input
-
Test authorization on password reset functionAttempt to access the password reset mechanism for a different user account without providing valid credentialsAffected if The system allows password reset requests for arbitrary user accounts without verifying the requestor's identity or authorization
A user is affected if Kiteworks MFT (Accellion MFT) version is 7.5 or any version lower than 7.6, and the password reset functionality is accessible on the web interface.
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 · scoped7.6
Upgrade Kiteworks MFT to version 7.6 or later to remediate this vulnerability.
7.6 or later
- 1. Identify current Kiteworks MFT version in use (confirm it is below 7.6)
- 2. Back up all current configurations, user data, and settings
- 3. Schedule a maintenance window for the upgrade
- 4. Download Kiteworks MFT version 7.6 or later from official channels
- 5. Execute the upgrade following Kiteworks upgrade documentation
- 6. Verify successful installation by checking the new version number
- 7. Test the password reset functionality to confirm the vulnerability is remediated
- 8. Validate that existing user accounts and configurations are intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24110 — 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-2022-24110 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