CVE-2026-43680
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 bypass a front-end restriction on OS Script schedule types and execute arbitrary operating system commands on the underlying host. 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 confidenceClaris FileMaker Cloud versions before 2.22.0.5 contain a Remote Code Execution vulnerability where users with Admin Console privileges can bypass a front-end restriction on OS Script schedule types to execute arbitrary operating system commands on the underlying host.
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.
-
Identify FileMaker Cloud versionLocate the FileMaker Cloud installation and check the version number. This is typically accessible via the Admin Console or by querying the product version through system documentation.Affected if The installed version is any version before 2.22.0.5 (e.g., 2.22.0.4, 2.21.x, earlier).
-
Verify Admin Console accessConfirm that your user account or any account in your environment has Admin Console privileges. Log into the Admin Console or review user role configurations.Affected if Admin Console privileges exist for any user in the environment.
-
Inspect OS Script schedule configurationsAccess the Admin Console and navigate to the schedule management area. Review any schedules configured with the OS Script type or similar operating system command execution capability.Affected if OS Script or command execution type schedules are present in the schedule list.
-
Review schedule creation and execution logsExamine Admin Console logs, system audit logs, or schedule activity logs for any recently created OS Script schedules or unexpected command executions, particularly those created outside of normal administration workflows.Affected if Logs show OS Script schedules that were not created through the expected front-end interface, or show unexpected command executions.
You are affected if FileMaker Cloud version is below 2.22.0.5 AND any user has Admin Console privileges, as the vulnerability allows privilege escalation to arbitrary command execution.
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 FileMaker Cloud to version 2.22.0.5 or later. Review Admin Console user access and monitor for any unauthorized schedule creation or command execution.
FileMaker Cloud 2.22.0.5
- Backup all FileMaker Cloud data and configurations before performing the upgrade
- Access the Admin Console or contact Claris support to initiate the upgrade to FileMaker Cloud 2.22.0.5
- Follow Claris official upgrade instructions for FileMaker Cloud
- Verify the upgrade was successful by checking the version number in the Admin Console
- Test that the Admin Console functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43680 — 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-43680 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