Clients and FileMaker users:
This is an important security advisory from Claris regarding recent password-spraying attacks targeting FileMaker Servers globally.
This is important! Pay attention!
There has been a recent large increase in AI attacks on FileMaker servers.

This graph shows one company’s attack logs in just one week: Thousands of attacks came each day in repeated waves searching for vulnerabilities.
Note: FileMaker is not any less secure than any other service. These attacks aren’t just happening to FileMaker servers, but they have increased on FM servers. FileMaker obscurity is no longer a defense against AI bots. If your application has a public-facing website or login, then it is being attacked.
Here’s a three-step process for dealing with the increased AI attacks on FileMaker Servers:
Part 1: Check for Attacks
Assume your server is continuously scanned by automated bots and monitor for active intrusion.
- Audit Server Logs: Inspect Admin Console logs and Data API logs for unusual traffic spikes, high request volume, or multiple failed login attempts originating from unknown IP addresses.
- Test Open Pathways: Verify public exposure by testing API endpoints (e.g., /fmi/data/vLatest/databases) and web access points (/fmi/webd).
If typing these URLs returns hosted database lists or open WebDirect login portals without authentication, your server is actively exposed. - Check for Unauthorized Changes: Review Admin Console API keys, automated schedules, and user accounts to verify no unknown keys, rogue accounts, or modified tasks were added during a password-spraying attempt.
- Identify Active Password Spraying: Monitor for rapid, repeated authentication failures across predictable account names (e.g., admin, Admin, Sales, Tech, Support).
Part 2: Check Vulnerabilities
Identify file-level misconfigurations, obsolete software, and exposed services before attackers exploit them.
- Audit Database File Settings: Inspect every hosted file to ensure auto-login is completely disabled, guest account access is turned off, and Encryption at Rest (EAR) is active.
- Review Account Privileges & Passwords: Identify all accounts with [Full Access] and trim unnecessary extended privileges (fmxml, fmrest, fmodata). Ensure no accounts rely on default, weak, or publicly visible passwords (such as employee names listed on your website). The AI bots are smart enough to review your website for key information.
Do any of your employees have more access privileges than they need. The best policy is to limit privileges where ever possible.
Are any employees able to login by memory without typing in a long 20-character password? Insist on random passwords. - Assess Software & PHP Versions: Verify whether FileMaker Server is running a supported major version (within Claris’s 2-year support window). If Custom Web Publishing, WordPress, or web hooks use PHP, check if the installed version is patched against unauthenticated code execution vulnerabilities, which we discussed in a previous issue.
- Inventory Active Connectors & Abandoned Files: Identify which services (WebDirect, Data API, OData, XML, Remote Desktop, SFTP) are actively used by your workflow, and check the server for old, unused, or forgotten database files.
Part 3: Change Security
Implement immediate administrative controls, server hardening, and long-term preventive measures.
- Execute Immediate Emergency Isolation (If Under Attack): Enable “Block New Users” in Admin Console Configuration > General Settings, disconnect active sessions, and temporarily restrict or block access to port 443 at the firewall to stop ongoing attacks.
- Harden Admin Console & Services: Change Admin Console credentials to a strong 20-character random password, generate new Admin API keys, enable “Filter Databases” in Configuration > FileMaker Clients, and turn off all unused connectors (WebDirect, Data API, OData, ODBC/JDBC, XML).
- Restrict Network Access: Place FileMaker Server behind a VPN or restrict port 443, Remote Desktop, and Admin Console access strictly to approved IP addresses at the firewall. Deploy a Web Application Firewall (WAF) or rate limiter for any remaining public services.
- Upgrade Software & Secure Backups: Update FileMaker Server and OS to supported versions, patch PHP immediately to secure versions (8.5.12+, 8.4.27+, 8.3.36+, or 8.2.35+), and verify off-network, immutable backups that an attacker cannot alter or delete.
- Implement 2FA for everyone. This step alone will make a drastic difference in server vulnerability.
Contact HighPower Data to get a security check.
We know what to look for and how to block the vulnerabilities.
Call me with any questions.
For more information, contact William Miller at 612-401-7550 or HighPowerData.com
Part 1: Check for Attacks
Part 2: Check Vulnerabilities
Part 3: Change Security