CVE-2024-27794
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 FileMaker Server before version 20.3.2 was susceptible to a reflected Cross-Site Scripting vulnerability due to an improperly handled parameter in the FileMaker WebDirect login endpoint. The vulnerability was resolved in FileMaker Server 20.3.2 by escaping the HTML contents of the login error message on the login page.
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 reflected Cross-Site Scripting (XSS) vulnerability existed in the FileMaker WebDirect login endpoint before version 20.3.2. The login error message displayed user-supplied input without proper HTML encoding, allowing an attacker to inject malicious scripts via a crafted parameter in the login request.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Check FileMaker Server versionIdentify the installed version of Claris FileMaker Server by accessing the Server Admin Console or checking the software installed on the host systemAffected if The installed version is below 20.3.2
-
Confirm WebDirect is enabledInspect the FileMaker Server configuration settings to determine whether the WebDirect module is currently enabledAffected if WebDirect is enabled and the server version is below 20.3.2
-
Verify WebDirect login endpoint is accessibleConfirm that the WebDirect login endpoint is reachable on the network, typically accessed via HTTP/HTTPS on the serverAffected if The login endpoint is accessible and the server version is below 20.3.2
The environment is affected if FileMaker Server version is below 20.3.2 and WebDirect is enabled and accessible, allowing user-supplied input in login requests to be reflected without HTML encoding in error messages.
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, which properly escapes HTML content in login error messages.
FileMaker Server 20.3.2 or later
- Backup all FileMaker Server data, databases, and configurations before proceeding with the upgrade
- Download FileMaker Server version 20.3.2 or later from the official Claris/FileMaker support site
- Stop the FileMaker Server services to prepare for the upgrade
- Run the FileMaker Server 20.3.2 installer and follow the on-screen upgrade instructions
- After installation completes, verify that FileMaker Server services start successfully
- Test the FileMaker WebDirect login endpoint to confirm the XSS vulnerability is no longer present by attempting to inject HTML/JavaScript in the login parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27794 — 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-27794 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