CVE-2026-43685
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 · uneditedA Remote Code Execution vulnerability in Claris FileMaker Cloud allowed a user with Admin Console privileges to inject arbitrary operating system commands through unsanitized input in the External ODBC Data Source connection test feature. This issue is fixed in FileMaker Cloud 2.22.0.5.
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 Remote Code Execution vulnerability in Claris FileMaker Cloud allows an authenticated Admin Console user to inject arbitrary operating system commands through unsanitized input in the External ODBC Data Source connection test feature. This is a command injection vulnerability requiring administrative privileges.
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< 2.22.0.5CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm FileMaker Cloud is deployedCheck your environment for installations of Claris FileMaker Cloud. Look for the FileMaker Cloud service or consult your infrastructure inventory.Affected if FileMaker Cloud is not present in the environment, this CVE does not apply.
-
Identify the installed versionAccess the Admin Console or check the FileMaker Cloud version information. The version is typically displayed in the Admin Console dashboard or can be retrieved via the product's built-in about/version information.Affected if The installed version is lower than 2.22.0.5, placing it within the affected range.
-
Verify Admin Console accessibilityConfirm whether the Admin Console web interface is accessible. Check if the management port (typically port 443 or configured custom port) is exposed and reachable.Affected if The Admin Console is accessible to untrusted or unauthorized users, the command injection vulnerability could be exploited by such users.
-
Check External ODBC Data Source configurationIn the Admin Console, navigate to the External ODBC Data Sources section. Examine whether any ODBC data sources are configured or if the connection test feature is available.Affected if The External ODBC Data Source feature is enabled and configured, the vulnerable connection test function is present and exploitable.
-
Review Admin Console user accountsAudit the list of users with Admin Console access. Identify accounts that have administrative privileges to the Admin Console.Affected if There are Admin Console users with privileges, they would have the capability to exploit this command injection flaw.
You are affected if FileMaker Cloud versions below 2.22.0.5 are installed AND the Admin Console with External ODBC Data Source functionality is accessible to authenticated administrative users.
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 · scoped2.22.0.5
Upgrade to FileMaker Cloud 2.22.0.5 or later. Until patched, restrict Admin Console access to fully trusted users only and consider network isolation of the management interface.
FileMaker Cloud 2.22.0.5
- 1. Back up all FileMaker Cloud configurations, databases, and critical data before initiating any upgrade.
- 2. Access the Claris FileMaker Cloud Admin Console or use the official cloud management interface.
- 3. Navigate to the software update or system maintenance section.
- 4. Initiate the upgrade to FileMaker Cloud version 2.22.0.5 or later.
- 5. Follow any on-screen prompts and allow the upgrade process to complete fully.
- 6. After upgrade completes, verify the External ODBC Data Source connection test feature is accessible and functioning properly.
- 7. Confirm the version number reflects 2.22.0.5 or higher in the Admin Console.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43685 — 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-43685 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