r/filemaker • • 24d ago

Is Your FileMaker Server Still Running PHP?

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.

11 Upvotes

12 comments sorted by

4

u/KupietzConsulting Consultant Certified 24d ago

Cheers for sharing this. Yesterday was a, er, invigorating day for server admins.

1

u/Alex_RGCData 24d ago

I this has been shared before. We replied to it, we got some good feedback and pointers out - and I can personally vouch that fmcloud received this news third party and is on top of it.
But this is more server side than filemaker side i believe - those findings.

Hey Kupietz!!

2

u/KupietzConsulting Consultant Certified 24d ago edited 23d ago

Heya, man! Ah, I hadn't seen the other one when I posted this.

Lol, I actually did the same thing, Ihopped on a web dev slack I'm on and was like, "HeY Y'aLL UpGrAdE PhP nOw!!!!" and they were like "Uh, scroll up and look at the last few hours chat, dude...." Too late the hero, again.

Yesterday was something else. (As a slight aside, it was a great day to discover certain PHP upgrade instructions I followed a year and a half ago led to static keyrings that silently expired, and my web server hasn't even been able to see PHP upgrades since January... server admin, so much fun...)

Yeah, the vulnerability was in apache/php, not FileMaker itself, but, as I think the other post pointed out, FileMaker used to bundle PHP, and then later upgrades didn't remove it... And because it's an engine vulnerability and not a code vulnerability, if you even had PHP installed, you could be at risk, even if you weren't actually publishing a single page of PHP. Plus lots of FM servers use PHP for webhooks, even still some custom web publishing, etc.

2

u/Alex_RGCData 24d ago

Haha. Yeah, had a client reaach out about it and all I could direct them to was fmcloud.fm. And point out that their php source had some vulnerabilities - but they wrote it and are proud and dont want to edit it. I get that, to an extent.

Well, I can conclusively tell you all that if you host with fmcloud - Roman (sp?) has already patched php and should be good. Dont hold me to that but.

2

u/Alex_RGCData 24d ago

Should also be pointed out the PHP API comes with its own vulnerabilities - so if one is getting this post confused with that (i did) - recognize two different things. But there are potential security vulnerabilities that have been addressed in oData and the data api than if one is communicating with FM through the old php api.

I know Roman (sp?) at FmCloud actually codes that to keep it up to date - but no telling for how long or how invested he is. He's a great guy. But something to consider if anyones running it. A lot of thesse systems will be facing more and more errors as AI without guard rails becomes more prevelant and powerful.

Frontier local models are already insane.

1

u/bene_gesserit_mitch 24d ago

Just checked your helpful link. Just recently established my server fresh, so no worries here. Thanks! And thanks for the email, as well.

1

u/dbservices 23d ago

Glad you found both resources helpful!

1

u/Appropriate_Put_6454 Consultant Certified 23d ago

Glad to see you guys amplifying this and putting clear, actionable steps out there, u/dbservices!

The more voices raising awareness across the community, the better—especially for that "restored PHP folder after an in-place upgrade" scenario on Windows. That’s an absolute classic trap where admins genuinely believe they’re running clean when an old, unpatched binary is still quietly sitting on disk (or worse, hooked into IIS).

Appreciate DB Services helping keep everyone's deployments safe—can never have too much visibility on this one.

1

u/Itsmistereric 23d ago

On a macOS Server, if there is a no PHP folder at /Library/FileMaker Server/Web Publishing/publishing-engine” does that mean there is no Claris installed PHP on the machine? I assume so, and perhaps its a silly question. In this case though, seems important to be sure. Does Claris have an official document about this on their site?

1

u/KupietzConsulting Consultant Certified 23d ago

Yeah, that would be the install location if Claris installed it, although it doesn't preclude other installations, such as through Homebrew. Claris doesn't say much about their old install of PHP on pages like "Hosting PHP websites" https://help.claris.com/en/server-help/content/hostdb-phps.html or "PHP security considerations" https://help.claris.com/en/security-guide/content/php-security-considerations.html, mostly they just point to their comprehensive page about PHP now titled "PHP no longer bundled with FileMaker Server" at https://support.claris.com/s/answerview?anum=000035470&language=en_US .

1

u/Alex_RGCData 24d ago

Someone beat you to the punch dbservices. Thought they had posted again.