dbcve.org
OpenkmApplication

CVE-2024-35475

MEDIUM · 6.4 CVSS v3.1 Published 2024-05-22
Fix available
A fix is available. Upgrade to after 6.3.12 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable

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
A Cross-Site Request Forgery (CSRF) vulnerability was discovered in OpenKM Community Edition on or before version 6.3.12. The vulnerability exists in /admin/DatabaseQuery, which allows an attacker to manipulate a victim with administrative privileges to execute arbitrary SQL commands.

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 · moderate confidence

CSRF vulnerability in OpenKM Community Edition's /admin/DatabaseQuery endpoint allows attackers to trick authenticated administrators into executing arbitrary SQL commands. The endpoint lacks anti-CSRF token validation, enabling malicious cross-origin requests from attacker-controlled pages.

MitigationImplement anti-CSRF tokens on the DatabaseQuery endpoint and enable SameSite cookie attributes. Consider requiring re-authentication for high-risk administrative operations like direct SQL execution.

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
OpenkmApplication
Affected:<= 6.3.12

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
High
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/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 OpenKM installation and version
    Locate the OpenKM installation directory and check the version file (typically version.xml, about.jsp, or the WAR file name). Alternatively, access the login page and check the footer or about section for the version number.
    Affected if The installed version is OpenKM Community Edition 6.3.12 or lower.
  2. Confirm /admin/DatabaseQuery endpoint exists
    Access the URL path /admin/DatabaseQuery (or /OpenKM/admin/DatabaseQuery depending on deployment) while logged in as an administrator. If the page loads with a SQL execution interface, the endpoint is present.
    Affected if The endpoint is accessible and loads a database query interface without requiring additional security verification.
  3. Verify anti-CSRF token validation is missing
    Inspect the HTML source of the /admin/DatabaseQuery page. Search for_csrf, token, or anti-csrf parameters in the form. Check if the form submission includes any token-based protection. Compare to other admin forms that may have this protection.
    Affected if The DatabaseQuery form has no CSRF token parameter and the backend does not validate one.
  4. Check SameSite cookie configuration
    Use browser developer tools or curl to examine the session cookie (JSESSIONID) Set-Cookie header. Look for SameSite attribute in the cookie configuration.
    Affected if The session cookie lacks SameSite=Strict or SameSite=Lax attributes, or has SameSite=None without Secure flag.
  5. Confirm administrator authentication is required
    Attempt to access the /admin/DatabaseQuery endpoint without authentication. Verify whether the endpoint is protected behind authentication or accessible only to users with administrative privileges.
    Affected if The endpoint requires admin authentication but does not implement additional CSRF protection on top of that authentication.

You are affected if you run OpenKM Community Edition version 6.3.12 or lower and the /admin/DatabaseQuery endpoint is accessible to administrators without CSRF token validation.

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.

From vendor data
Upgrade available Upgrade to a release after 6.3.12
Interim mitigation

Implement anti-CSRF tokens on the DatabaseQuery endpoint and enable SameSite cookie attributes. Consider requiring re-authentication for high-risk administrative operations like direct SQL execution.

Fix this in Openkm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35475 — 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-2024-35475 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