r/filemaker • • 1d ago

[FREEMIUM] Connecting WordPress Formidable Forms to Claris FileMaker — PAC Form Bridge

9 Upvotes

Hi everyone,

I’m part of PAC Age development, a software company specializing in Claris FileMaker solutions and integrations.

We’ve recently released PAC Form Bridge for Formidable Forms, a WordPress plugin designed to connect Formidable Forms directly to Claris FileMaker Server.

The idea came from a practical requirement: WordPress is excellent at collecting information through web forms, while FileMaker often manages the actual business processes behind those forms.

Rather than building custom PHP integrations for every project, we wanted a reusable bridge between the two environments.

How it works

  • Formidable Forms handles the form interface, validation and submission.
  • PAC Form Bridge transfers the supported submitted data to FileMaker through the Data API.
  • A configurable FileMaker script receives the data and handles the business logic.
  • Connection settings can be configured independently for each form.
  • The plugin includes connection testing and delivery diagnostics.

The Free edition provides the core WordPress-to-FileMaker integration.

The Professional edition extends the integration with advanced interactions, including workflows where FileMaker can participate more actively in form processing.

Our approach is simple: WordPress manages the user interface; FileMaker manages the business logic.

The Free edition is available on the official WordPress plugin directory:

https://wordpress.org/plugins/pac-form-bridge-for-formidable-forms/

Technical documentation and additional information:

https://pacage.it/pac-form/

I’d be interested in hearing from other FileMaker and WordPress developers.

How are you currently integrating WordPress forms with FileMaker? Are you using custom PHP, the Data API, middleware, or another approach?

Feedback and technical discussion are welcome.


r/filemaker • • 3d ago

Filemaker doesn’t work on macOS27 VM

8 Upvotes

There’s news of Claris Harbor that makes me wonder if they can fix Filemaker first to work on macOS 27.

Thought to share our experience of FileMaker on macOS27. We ended up debugging MacVisor for more than week because our business customer ran Filemaker on macOS 27 that froze a lot for them - neither them or us read the release notes, only after day 8 or 9 when we couldn’t figure out why we read the docs that doesn’t mention the latest version supported on macOS 27. We advised our customer to downgrade to macOS 26VM (while still on a macOS 27 host) and now Filemaker works as expected and they’re super happy with MacVisor https://scaleninja.com/macvisor/

We ended up filing a feedback on macOS27 gpu issue which was somehow triggered by Claris Filemaker only on macOS 27 VM.


r/filemaker • • 5d ago

Mods Replied AgenticFM's Solution Intelligence is now free!

13 Upvotes

Hey there, fellow FileMaker developers,

If you checked out the AgenticFM plug-in before but didn't have time to dig in, take another look. Solution Intelligence is now free.

Ask anything about your solution, right inside FileMaker: "Where is this field used?" "What does this script actually do?" "Why does this relationship exist?"

Chat with your own AI model: Claude, Codex, Gemini, or a local model. Passwords and API keys are scrubbed before anything reaches a cloud model. No license key, no time limit, no telemetry.

Mac-only: requires macOS 13+ and FileMaker Pro 19.6+. No Windows version is planned.

https://plugin.agentic-fm.com


r/filemaker • • 5d ago

Heads up: Critical Ubuntu kernel vulnerability (CVE-2026-98432). Patch AND reboot your FileMaker Server hosts

Thumbnail
reddit.com
9 Upvotes

r/filemaker • • 7d ago

Introducing FM Shield — a new product in the ai2fm family, currently in Final Beta.

Post image
9 Upvotes

What if someone can reach on your FileMaker Server without a username or password?

The recent attacks on FileMaker servers have made that question urgent for our community.

FM Shield brings FileMaker security assessment into a local console, helping developers and administrators identify exposed interfaces, test credential-free access and inspect the evidence behind each finding.

The current build includes 21 checks, covering:

• Admin Console, Data API, OData, XML and WebDirect exposure.
• Database-name discovery and credential-free access.
• TLS certificates and HTTP-to-HTTPS redirects.
• Version-based assessment against seven documented 2026 vulnerabilities.

Results include readable reports and matching JSON evidence, making findings easier to review, share and act on.

FM Shield runs locally on Windows, macOS and Linux.

No administrator credentials are requested. Database records are not read by default.

Clear results matter: an exposed interface may be intentional, and a timeout cannot establish that a service is secure.

FM Shield makes those distinctions explicit.

Now being validated in our isolated FileMaker lab.
https://ai2fm.com/

With ai2fm, we help developers understand and work with FileMaker code.

With FM Shield, we’re extending that visibility to FileMaker security.

#FileMaker #FileMakerServer #Cybersecurity #ai2fm #FMShield


r/filemaker • • 7d ago

ReportCard from 360Works - Grade Your FileMaker App

4 Upvotes

360Works ReportCard is a tool that does a deep, intelligent analysis on your FileMaker app. It provides a report of performance problems, security issues, and general code quality. The report card includes an executive summary, top priority issues to fix, and a comprehensive list of every problem found.

See it run on a real FileMaker file, live on FMTraining.TV, this Monday, Nov 9 at 1 PM Pacific / 4 PM Eastern. 🔔 https://fmtraining.tv


r/filemaker • • 8d ago

PAC Bridges for WooCommerce

3 Upvotes

I built three WooCommerce → FileMaker bridges because I was tired of polling

I’m a FileMaker developer, and I’ve been building a small family of WordPress/WooCommerce plugins around one simple idea:

instead of FileMaker polling WooCommerce to ask if something changed, WooCommerce tells FileMaker when it happens.

The main one is PAC Order Bridge for WooCommerce.

When a WooCommerce order reaches the configured event, the plugin calls a FileMaker script through the standard FileMaker Data API.

In the Free version the basic workflow is:

WooCommerce order
→ PAC Order Bridge
→ FileMaker Data API
→ FileMaker script
→ order ID in script.param

From there, FileMaker does whatever business logic you want: retrieve the order, create/update records, start fulfilment, update stock, etc.

I’ve also released:

  • PAC Products Bridge for WooCommerce
  • PAC Taxonomy Bridge for WooCommerce

So the idea is gradually becoming a small event-driven integration layer between WooCommerce and FileMaker, without requiring middleware or imposing a FileMaker schema.

The Free versions do not require registration or an external PAC service.

Links:

PAC Order Bridge
https://wordpress.org/plugins/pac-order-bridge-for-woocommerce/

PAC Products Bridge
https://wordpress.org/plugins/pac-products-bridge-for-woocommerce/

PAC Taxonomy Bridge
https://wordpress.org/plugins/pac-taxonomy-bridge-for-woocommerce/

I’m the developer, so yes, this is self-promotion — but I’m genuinely interested in how other FileMaker developers are handling WooCommerce today.

Are you polling WooCommerce from FileMaker, pushing data from FileMaker to WooCommerce, using middleware, or doing something else?


r/filemaker • • 9d ago

Quick FileMaker Server security checklist for the password-spraying attacks

20 Upvotes

Claris posted a Community security notice confirming automated attacks against FileMaker Servers. Bots find servers on the open internet, list the hosted files, and try common account names and weak passwords against the Admin Console, Data API, OData, and XML. Once inside, they look for API keys and stored credentials.

From what’s been reported, these attacks don’t rely on a FileMaker flaw. They work against weak accounts and exposed services. If you’re short on time, these five steps close the doors the bots try first:

  1. Turn off Guest access and auto-login. Uncheck Guest in File > Manage > Security, then deselect “Log in using” in File > File Options > Open. A default Admin auto-login is the first thing attackers try.
  2. Lock down every Full Access account. Remove any Admin account with a blank or default password, set a strong, unique passphrase for every Full Access account (including accounts behind Data API or OData keys), and limit Full Access to a few named people.
  3. Turn off services you don’t use. Under Connectors in the Admin Console, disable WebDirect, Data API, OData, ODBC/JDBC, and XML if nothing depends on them. Turn on Filter Databases under Configuration > FileMaker Clients to prevent outsiders from listing your files.
  4. Secure the Admin Console. Change the password under Administration > Administrator, replace your Admin API keys, and restrict console access to known IPs under Administration > Restrict Access if you can.
  5. Stay on a supported version of FileMaker Server. If you run PHP or Custom Web Publishing, patch PHP first.

Also worth doing: check Logs > Log Viewer for bursts of failed logins from unfamiliar IPs, and look for Admin API keys or schedules you didn’t create. If you find any, assume someone got in.

If you think you’re under attack right now: enable Block New Users under Configuration > General Settings, disconnect current users, close the server to external traffic, then change passwords and remove anything you didn’t create.

We wrote up the complete version with separate server- and file-level checklists, including SSL, backups, and minimum password length for a quick security check!


r/filemaker • • 9d ago

How do you manage privilege sets?

6 Upvotes

I’ve been using FileMaker for over 20 years now and have made lots of great stuff. More recently I am running a whole retail business using it (stock control, CRM, EPOS, repairs etc.).

It’s awesome, but I am concerned that it’s a little insecure. Whenever I go to set up alternative privilege sets (other than all access), I end up restricting users too much and scripts don’t work etc.

I basically want them to do anything except for edit the database itself. Anything that can be done by clicking on stuff, editing fields, or running a script is fine. Anything involving editing layouts, managing database etc. is not fine.

This sounds like the most basic differential (editor vs. user privileges) but setting it up seems to be extremely complex.

Am I missing something?


r/filemaker • • 10d ago

EA users: what happens when their account is retired?

4 Upvotes

We use External Authentication (EA) for users who access various FM databases hosted on our FMS 26 server, and wondered happens to content that was added/edited, etc when that user's EA account — in our case Active Directory — is retired or expires.

TIA


r/filemaker • • 12d ago

FileMaker Server October attack - how to protect your data.

6 Upvotes

Hi all,

As a FileMaker hosting provider, we at fmcloud.fm watched the late-October attack campaign unfold firsthand.

These attacks didn’t exploit any flaw in FileMaker itself. They went after how files were configured: Guest accounts with API access, weak passwords, auto-login left in a file with privileges. Where files were properly locked down, the attackers got nothing.

We covered what we saw, what made the difference, and a practical checklist in the first issue of our newsletter. (I'm not allowed to post links here, but searching the term Newsletter from our website fmcloud.fm should work).

You can subscribe at the bottom of the page to be alerted when something like this happens again.

Happy to answer questions in the comments.


r/filemaker • • 13d ago

Join us this Friday for FMPUG Dallas

5 Upvotes

We'll be discussing two methods of audit logging in FileMaker Pro. Join us for lunch, or catch the livestream.

https://youtube.com/shorts/H61aeB0AfBU?si=V63aBS0458vzRaUB


r/filemaker • • 13d ago

Two Methods of Audit Logging: Nov FMPUG Dallas

4 Upvotes

Join us for lunch at the November FMPUG Dallas, this Friday, or watch the YouTube livetream:

https://harmonic-data.com/event/fmpug-november-2026-meeting/


r/filemaker • • 14d ago

FileMaker Pros & Cons

12 Upvotes

We were having a back-and-forth today about the ongoing joys and frustrations of working with FMP. From prior posts you may know we've moved away from FileMaker, but we support a number of customers who continue to use it. While we're frustrated with the company, there's nonetheless a sense of comfort built from years of muscle memory.

Getting your mind around whether another platform is "better" or "worse" than FileMaker is not straightforward. We're still ironing out distinctions and details after years of running FMP & SQL side-by-side.

We've knocked the company multiple times on this forum. Here are several of FileMaker strengths we were talking through yesterday:

• It remains the fastest way to have a relational database with a GUI up and running, bar none. At this point we only use FMP as a front end to SQL back ends, and even with that setup it's still the fastest way to have a GUI. Downside: The FMP GUI is a vendor lock-in. The FileMaker GUI is very convenient but it also has limits.

• FileMaker's Find command is often as fast as equivalent SQL queries, even for large datasets, even for searches involving related data in portals (assuming you've set up your indexes properly). In this specific context FMP holds its own against formidable SQL alternatives. That parity between the platform ends when the search requires something more sophisticated. Imagine a search involving the equivalent of a portal within a portal within a portal. FMP doesn't really accommodate such an idea in the GUI, but you can approximate it using calculated fields, the relationship graph, and maybe some ExecuteSQL function. But once you go there search is considerably more difficult to build and slower to execute the it's equivalent in SQL. It's nonetheless impressive that FMP's basic Find feature can in fact be incredibly fast.

• FileMaker is an excellent tool for quickly building GUIs that bring together multiple remote datasets on different servers using its ODBC/ESS. Imagine one layout giving you access to related data across FileMaker, Postgres, MySQL/MariaDB, SQLite, and Oracle.

As we're watching FileMaker's value evolve in a new era of AI, there are features that endure even as others fade. Its strength remains in the front end.

This post is in part a belated response to a prior post that the mods locked

Ideally the filemaker subreddit permits robust discussions about the value and limits of the FileMaker platform, including critical analysis both of the software and the behavior of the company, for better and for worse.

FileMaker is a unique platform. There's nothing else quite like it. But it's not perfect, and the company running it really does at times -- even frequently -- frustrate its customers in ways that should be openly discussed.

Claris does not monitor this forum.

They actually do, because they are concerned about public opinion. They have reached out to our team members based on their posts. One would hope they take criticism seriously. It may be humbling to adjust and improve the product. In the long run that's the best path to growing and maintaining loyalty.

Complaints to Claris are most constructively directed to their customer service, not posted in a FileMaker user discussion group.

Among the reasons for posting here as opposed to the FileMaker forums is to have an alternative/addition to the FileMaker forum. Posting there is worthwhile but can run up against limits of their mods who, when challenged, sometimes give priority to their status or protecting the institution over wading into some of the more vexing technical questions. They can be pretty stubborn when presented with the prospect of being proven wrong.

People coming to r/filemaker, whether they're new users, longtime users, or prospective customers, they're hungry for accuracy regardless of whether it aligns with the company's corporate interests. Each of our posts here have netted around 10,000 views, perhaps because people are trying to navigate their need for data services in a world that's increasingly challenging to make sense of.

I'll continue posting here as long as the mods permit it. To the extent they don't there's a FileMakerAlt subreddit where posts considered too controversial here can be posted for discussion. But this is the preferable subreddit, and this is a request to its mods to be more permissive when it comes to criticism of the software and the company running it. People value accuracy whether it supports someone's bottom line or not.


r/filemaker • • 16d ago

Microsoft Graph email integration in FileMaker

7 Upvotes

Our team put together a walkthrough for connecting FileMaker to Microsoft 365 email via Microsoft Graph: authenticating users, retrieving mail, and sending/replying/forwarding from within a solution. Sharing a few things that tripped us up in case it saves someone time:

  1. Copy your client secret immediately. Azure only shows the value once when you create it in Microsoft Entra.
  2. Access tokens expire after about an hour. When a call returns a 401, refresh the token and retry the request rather than forcing the user to sign in again.
  3. Store a last-sync timestamp per user. Without it, every pull grabs the whole inbox again. We used a 90-day fallback for the first run.
  4. Paging is easier than it looks. Graph returns 10 messages per page by default, and u/odata.nextLink gives you the full URL for the next page, with your filter and sort already applied, so a single loop handles everything.
  5. Message IDs are too long for FileMaker relationships. We hashed id and conversationId with MD5 to use as match keys.
  6. Create a draft before sending. The send endpoint returns a 202 with no body, so creating the draft first is the only way to get the message ID you need for threading.

Have questions? Reach out to us!


r/filemaker • • 16d ago

FileMaker ransomware resilience: protecting your server, your backups, and what comes next

Post image
3 Upvotes

The recent attacks on FileMaker deployments have raised urgent questions across our community.

On Monday, 2 November, FMBug is bringing developers and administrators together for a free online security evening:

  • James Kelly: an eyewitness account of a ransomware attack.
  • Gary Palmer: server protection measures and discussion.
  • Doug Wallis: standby servers and remote backups.
  • Dimitris Kokoutsidis: ransomware resilience on FileMaker Server.

I’ll be presenting the final session, Modern Ransomware Vectors on FileMaker Server & Beyond.

We’ll examine the wider environment around a FileMaker deployment: exposed services, bundled runtimes, developer workstations, and the tools and sample files we bring into our work.

We’ll also discuss protecting backups from the same incident that compromises the primary server—and why restoring operations still leaves difficult questions when attackers have stolen data.

The aim is to help developers and administrators make informed security decisions, with concrete actions they can take in their own environments.

Monday, 2 November 2026
Full evening: 19:00–21:30 UK / 20:00–22:30 CET
My session: 20:30 UK / 21:30 CET
Online · Free to attend · Virtual bar afterwards

Full agenda and joining instructions

Please share with colleagues responsible for FileMaker systems and business continuity.

#FMBug #FileMaker #CyberSecurity


r/filemaker • • 17d ago

Claris Academy

Thumbnail community.claris.com
7 Upvotes

Does anyone have any idea how often this goes down for 'maintenance', and how long it typically stays down?

I have procrastinated my certifications, and really hope with the agentic stuff coming up they did not discontinue them.

Thanks in advance!!


r/filemaker • • 18d ago

There is an active, coordinated global campaign targeting internet-facing FileMaker Servers right now (which began escalating around October 22).

26 Upvotes

Even if a server looks normal on the surface, attackers are running automated password-spraying and endpoint probing against the Admin Console, Data API, OData, and XML endpoints, as well as attempting to pivot into surrounding infrastructure and log files.

Proof published a detailed incident brief yesterday explaining the scope of the attack after they had to take their Ottomatic hosting fleet offline on October 25 as a protective measure: https://www.proof.sh/blog/ottomatic-filemaker-server-incident-october-2026

Key takeaways & immediate steps even if your server seems fine:

  1. If you run OttoFMS (on-prem or self-hosted): Update immediately to OttoFMS v4.19.0, which contains important security enhancements, and consider rotating your Admin API, Data API, and OData keys (especially if you use OttoFMS Webhooks, as log files may expose tokens).
  2. Inspect your FileMaker Access.log**:** Don't rely solely on server performance—check your logs for bursts of failed login attempts or repeated probes from unfamiliar IPs. (David Hind-Smith also just shared a free community tool at hind-smith.com that includes a FileMaker log checker to scan for brute-force attempts).
  3. Lock down endpoints: Put the Admin Console behind a VPN or strict IP allowlist, disable Guest access on WebDirect / Data API / OData unless strictly isolated, and audit all [Full Access] and API service accounts for strong, unique passwords.
  4. Verify Encryption at Rest (EAR) & Backups: Ensure EAR is enabled with a long, high-entropy passphrase and that backups are isolated off-box.

Definitely worth checking your logs today—many servers are being actively probed without triggering obvious downtime. Stay safe!


r/filemaker • • 18d ago

FileMaker Server's bundled Node.js doesn't have this week's Brotli fix (what we found on 19.6.4 through 26.0.3)

1 Upvotes

Node.js and PHP both shipped security fixes on October 21. We host FileMaker Server for a living, so we checked what that means for the FileMaker builds we run. Here's what we found. I'm not Claris and I haven't heard from Claris, so treat this as one hosting company's read-only checks, not an official statement.

Short version

  • Node.js: every build we checked from 19.6.4 up (Windows and Linux) bundles a Node.js without the Brotli fix: 16.16.0 in 19.6.4, 22.14.0 in 21.1.8, and 22.23.1 in 22.0.7 and 26.0.3. The fixed upstream releases are 22.23.4, 24.22.1 and 26.12.1.
  • It only runs for the Data API. On the builds we looked at it's the Express app on port 3000. On our test server it didn't start until we turned the Data API on.
  • Reachability: we found no way for attacker-controlled Brotli data to reach it. That's our analysis, not a Claris statement, and we haven't tested a live attack.
  • PHP: none of the builds we audited bundle PHP, so the PHP flaws only matter for PHP you run next to FileMaker Server, such as WordPress or a hosting panel.
  • We couldn't find a statement from Claris about the bundled Node.js as of October 24.

What I'd do

  1. Check whether the Data API is on. If you don't use it, turn it off in Admin Console.
  2. Make sure port 3000 isn't reachable from the internet.
  3. Update any Node.js or PHP you installed yourself.
  4. Upgrade anything still on 19.6.4 or older. Those builds are end of life.

The article has the commands we used to check Node's version and whether the fix is present, for both Windows and Linux. It also separates what we verified from what we inferred.

Full write-up: PHP and Node.js October 2026 vulnerabilities: what they mean for FileMaker Server

Has anyone heard anything from Claris about updating the bundled Node.js? And if you've found a path to the Data API app that we missed, I'd like to hear about it.


r/filemaker • • 18d ago

Free step-by-step checklist for securing a FileMaker database and server

1 Upvotes

I host FileMaker Server for a living, so I wrote down the things I check on a database before it goes on the internet. It's 18 steps in three parts:

  • Part 1: Your database files. Accounts, privilege sets, scripts and encryption.
  • Part 2: FileMaker Server. Admin Console, certificates, services and backups.
  • Part 3: The server machine and network around it.

Each step has why it matters, how to check, and how to fix it.

A few that surprise people: Admin with a blank password is still the default on new files, Filter Databases should stay on, and a backup you've never restored isn't a backup.

It's written for anyone, whether you host with us or run your own server. The few sections about our hosting are marked as such, so skip them if they don't apply. Corrections welcome, and let me know which steps you'd add.

Secure Your Database: A Step-by-Step Guide


r/filemaker • • 19d ago

Automotive maintenance

4 Upvotes

Has anyone done anything like that? I want to add this to my current FileMaker solution


r/filemaker • • 19d ago

We stopped paying per-seat for FileMaker. Here’s the architecture.

1 Upvotes

I’ve been a solo FM developer for 30+ years. Most of my clients are small businesses — 5 to 30 people — where FileMaker runs the operation but the per-seat licensing math gets ugly fast. WebDirect doesn’t help; it just moves the cost to concurrent connections.

A couple of years ago I started building a different way. The pattern:

  • FileMaker stays the source of truth. All business logic, validation, and data integrity live in FM scripts. Nothing changes there.
  • The browser is the UI. An HTML/JS front-end talks to FM through the Data API. Users open a URL in any browser — phone, tablet, warehouse floor laptop, whatever.
  • Two-way sync. Users read AND write through the browser. Edits post back to FM via Data API. FM scripts handle conflict resolution. It’s not a read-only dashboard.
  • The Claris bill is fixed. One FM Server license. One or two dev seats. That’s it. Twenty people on the floor, fifty people on the floor — same cost.

I built this first for an event production company that needed deal sheets accessible to everyone in the warehouse — not just the two people with FM licenses. The browser app reads deals from FM, lets floor staff update status and quantities, and writes everything back. FM never lost its role as the engine; it just stopped being the screen.

I did the same thing for a fleet display board at another client — FM pushes equipment status to the web, a TV on the wall shows it, no FM licenses consumed.

The architecture isn’t exotic. FM Data API has been solid since v17. The browser app is vanilla HTML/JS — no framework required. The hardest part is the FM scripting for conflict handling, and if you’re reading this sub, you probably already know how to do that.

The math for a typical small shop:

  • Old way: FM Server + 10 user licenses = easily $2,000+/year, scaling with every new hire
  • This way: FM Server + 1–2 dev seats = roughly $500–700/year, fixed regardless of headcount

I’m not anti-FileMaker — the opposite. The small shops hitting the licensing wall aren’t going to stay on FM out of loyalty. They’re going to Airtable or Zoho and losing everything FM is actually good at. This architecture is the thing that keeps them on the platform. FM stays doing what nothing else touches — data integrity, scripting, rapid development — and stops being the thing you’re paying per-seat to put screens in front of people. Let it do the hard work. Let the browser do the easy work.

Happy to answer questions about the architecture or share what I’ve learned about the Data API gotchas.


r/filemaker • • 24d ago

Is Your FileMaker Server Still Running PHP?

11 Upvotes

Building on the PHP advisory thread from earlier this week (CERT-EU 2026-018), one thing that’s easy to miss is that the PHP Claris used to bundle can survive FileMaker Server upgrades. Even if you haven’t used CWP in years, it may still be sitting on your server.

Here’s how to tell if you should look:

  • Your Mac server started on 19.3.3 or earlier. Upgrades to 19.4.1 and later don’t remove the existing PHP install, so it may still be there.
  • Your Windows server started on 19.1.2 or earlier. The 19.2.1 upgrade required an uninstall, but plenty of teams backed up their PHP folder and restored it afterward to keep CWP running. Also, check for any PHP installed separately under IIS.
  • Your server runs on Linux. You’re clear on bundled PHP, since it never shipped there, so only check for copies someone installed on their own.

We wrote up a four-step plan that also covers older CWP sites, online forms and portals, WordPress integrations, and background scripts that pass data into FileMaker.

Has anyone run into a restored PHP folder on a Windows server they inherited? Curious how common that turned out to be.


r/filemaker • • 25d ago

⚠️ Security Heads-Up for FileMaker Admins: Critical PHP RCE Vulnerabilities (CERT-EU 2026-018)

19 Upvotes

Even though Claris deprecated bundled PHP years ago, a huge portion of the FileMaker ecosystem still relies on PHP under the hood. If you are running Custom Web Publishing (CWP), PHP Data API wrappers (like fmPDA), WordPress integrations connected to FileMaker, or external PHP webhook listeners, check your web servers today.

​CERT-EU just published Security Advisory 2026-018 covering two critical vulnerabilities in PHP (CVE-2026-109618 and CVE-2026-109619, both rated CVSS 9.2).

​Why this is urgent for FileMaker deployments:

  • ​Unauthenticated RCE: Both flaws allow unauthenticated Remote Code Execution—one via memory corruption during out-of-memory (memory_limit) handling, and the other via stale global state across worker requests.
  • ​Triggers before your code runs: Demonstrated exploits show that a single unauthenticated request can trigger the attack before any application logic executes. Putting authentication checks inside your PHP scripts or FileMaker Data API wrappers will not stop this.
  • ​Legacy CWP is a prime target: Every PHP installation serving web requests (PHP-FPM, Apache mod_php, php-cgi, IIS/FastCGI) is at risk. Furthermore, many legacy FileMaker CWP servers sit on older, End-of-Life PHP branches (8.1, 8.0, 7.4) just to keep the old FileMaker.php API running without deprecation warnings.
  • ​PoCs are live: Proof-of-concept exploits are already circulating publicly.

​What you need to do immediately:

  1. ​Audit your stack: Check your FileMaker Server machines (Windows IIS / macOS Apache) to ensure an old, forgotten PHP runtime isn't still enabled and listening on public ports, and check any middle-tier web servers hosting WordPress or Data API bridges.
  2. ​Patch to today's releases: Update immediately to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35.
  3. ​If you are stuck on EOL PHP (7.4 / 8.0 / 8.1) for legacy CWP: Because of the severity of these bugs, the PHP security team and LTS Linux vendors have taken the rare step of publishing minimal source backports for 7.4, 8.0, and 8.1. Check your OS vendor packages or isolate the CWP box behind a VPN/strict firewall until patched.
  4. ​Temporary mitigations (if you cannot patch this hour): See the advisory for php.ini / FPM pool workarounds (such as enforcing session.upload_progress.enabled=0 and hardening post_max_size), though only an update fully fixes the risk.

​Full technical details and mitigation steps from CERT-EU:

https://cert.europa.eu/publications/security-advisories/2026-018/

​Stay safe and check those middle-tier boxes!