CVE-2024-27790
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 · uneditedClaris International has resolved an issue of potentially allowing unauthorized access to records stored in databases hosted on FileMaker Server. This issue has been fixed in FileMaker Server 20.3.2 by validating transactions before replying to client requests.
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 confidenceFileMaker Server had a validation issue where transactions were not properly validated before replying to client requests, potentially allowing unauthorized access to sensitive database records. The fix implements proper transaction validation on the server side before responding to client queries.
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< 20.3.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify installed FileMaker Server versionOpen FileMaker Server Admin Console and navigate to the Server Diagnostics or About page, or run 'fmsadmin -v' from the command line if fmsadmin is in your PATHAffected if The reported version is below 20.3.2 (e.g., 20.x versions prior to 20.3.2, or any version 19.x and earlier)
-
Verify FileMaker Server is running and accepting client connectionsCheck if the FileMaker Server service (fmserver or FileMaker Server) is running via Services control panel (Windows) or launchd (macOS), or attempt to access the Admin Console via web browser on port 16000Affected if The server is actively running and serving client requests, which means transaction handling is in use
-
Confirm the deployment uses FileMaker Server (not FileMaker Pro)Review the installed software list or check the Admin Console - FileMaker Pro is the client application while FileMaker Server is the server component. The vulnerability exists in FileMaker Server specifically, not the client.Affected if The affected product is Claris FileMaker Server (server component) rather than just FileMaker Pro client
If FileMaker Server is installed and running with a version lower than 20.3.2, the environment is vulnerable to improper transaction validation that could allow unauthorized database record access.
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 · scoped20.3.2
Upgrade FileMaker Server to version 20.3.2 or later to implement server-side transaction validation and prevent unauthorized record access.
FileMaker Server 20.3.2
- Backup all FileMaker databases and server configuration files before proceeding with the upgrade
- Ensure the server meets the system requirements for FileMaker Server 20.3.2
- Download FileMaker Server 20.3.2 from the official Claris website or your authorized download location
- Stop the FileMaker Server services (or ensure no active connections to hosted databases during the upgrade)
- Run the installer for FileMaker Server 20.3.2 and follow the on-screen installation prompts
- After installation completes, verify the server status through the FileMaker Server Admin Console
- Confirm that databases are accessible and the access control fix is functioning by testing record access permissions
- Review the FileMaker Server Admin Console for any configuration changes needed post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27790 — 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-2024-27790 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