dbcve.org
KiteworksApplication · Accellion

CVE-2021-31586

HIGH · 8.8 CVSS v3.1 Published 2021-06-23
Fix available
A fix is available. Upgrade to 7.4.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Accellion Kiteworks before 7.4.0 allows an authenticated user to perform SQL Injection via LDAPGroup Search.

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 confidence

SQL injection vulnerability in the LDAPGroup Search functionality of Accellion Kiteworks prior to version 7.4.0, allowing authenticated users to inject and execute arbitrary SQL queries through insufficient input sanitization.

MitigationUpgrade to Accellion Kiteworks 7.4.0 or later to obtain the vendor patch. If immediate patching is not feasible, restrict network access to the Kiteworks application and implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns in LDAPGroup Search requests.

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
KiteworksApplication
Affected:< 7.4.0

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Kiteworks version
    Check the Kiteworks application version through the admin interface, system information page, or by querying the application's built-in version endpoint if available. Compare the version number against the 7.4.0 release.
    Affected if The installed version is any release prior to 7.4.0 (e.g., 7.3.x, 7.2.x, earlier).
  2. Confirm LDAPGroup module is configured
    Review the Kiteworks configuration to determine if the LDAPGroup Search functionality is enabled. This may be visible in the admin panel under LDAP/Directory integration settings, or by examining the application's module configuration files.
    Affected if LDAPGroup Search is enabled and the application is configured to query an LDAP directory for group membership.
  3. Check for unauthorized SQL query execution
    Review application and database logs for suspicious or unexpected SQL queries originating from the LDAPGroup Search feature. Look for SQL syntax patterns, UNION SELECT statements, or anomalous queries that differ from normal group lookup operations.
    Affected if Log analysis reveals SQL injection payloads or abnormal database queries matching LDAPGroup Search user sessions.
  4. Inspect for signs of database compromise
    Examine the database for unauthorized records, modified data, or unexpected tables that could indicate successful SQL injection exploitation. Check for any newly created administrative accounts or modified user permissions.
    Affected if Unexpected database changes, unauthorized accounts, or data exfiltration patterns are found in the Kiteworks database.

A system is affected if it runs Accellion Kiteworks version below 7.4.0 AND has the LDAPGroup Search feature enabled, making SQL injection possible through the LDAP query interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.4.0 or later
Fixed in 7.4.0
Interim mitigation

Upgrade to Accellion Kiteworks 7.4.0 or later to obtain the vendor patch. If immediate patching is not feasible, restrict network access to the Kiteworks application and implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns in LDAPGroup Search requests.

Recommended fix Moderate confidence

7.4.0

  1. Upgrade Kiteworks to version 7.4.0 or later to resolve the SQL injection vulnerability
  2. Verify the upgrade was successful by confirming the installed version
  3. Test that the LDAPGroup Search functionality works correctly post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kiteworks Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-31586 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-31586 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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