Insights

Two critical PHP flaws: a response checklist for businesses

22 October 2026

Use this PHP security checklist to identify affected websites, confirm official fixes, assign patch ownership and test business applications after updates.

Two critical vulnerabilities in PHP could allow attackers to execute code without signing in, according to ARN’s report on the emergency patch announcement. The report attributes the fixes and urgent patching advice to the PHP Foundation. Businesses running PHP-backed websites, customer portals or other applications should promptly establish their exposure.

This PHP security checklist gives Australian businesses a practical response sequence: find the runtime, verify the applicable advisory, name the person responsible for patching, and test the result. Updating a website’s content management system alone does not establish that its underlying PHP runtime is fixed.

1. Start your PHP security checklist with a runtime inventory

Ask your hosting provider, developers and IT team to identify every service that processes web requests through PHP. Do not limit the search to your main website.

Include online shops, booking platforms, customer portals, internal applications, staging sites, old campaign sites and administrative interfaces. Vendor appliances may also contain PHP, even when your team cannot inspect or update the runtime directly.

Create one response register with these fields:

| Record | What to capture | | --- | --- | | Service | Website, application or device and its business purpose | | Exposure | Public internet, restricted access or internal only | | Runtime | PHP branch, exact package build and web execution method | | Platform | Hosting account, server, container image or vendor product | | Ownership | Business owner, patching team and escalation contact | | Status | Advisory checked, fix planned, deployed and verified |

A server can have several PHP versions installed. Running `php -v` checks the command-line executable being invoked, not necessarily the runtime handling website traffic. Have an administrator confirm the version used by each active site, worker pool or container. Avoid leaving public diagnostic pages online: they can disclose configuration details.

2. Confirm exposure against official PHP information

Use news coverage as the trigger for investigation, not the final authority for a production change. Start with the PHP Foundation and PHP project release information, then check the security notices from your operating system, hosting or product vendor.

ARN identifies the reported vulnerabilities as CVE-2026-109618 and CVE-2026-109619. It lists PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 as patched releases. Treat those identifiers and version numbers as reported details to verify against the original advisories before choosing a package or marking a system resolved.

The report describes exposure across PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed, with particular concern around mod_php. Do not assume a different web server arrangement removes the need to investigate.

For each installation, establish:

  • Whether the official advisory applies to its branch and configuration.
  • Which upstream release or vendor package contains the fix.
  • Whether the vendor has backported the fix into an older-looking package version.
  • Whether the runtime is still supported and receiving security maintenance.
  • Whether service restarts, worker recycling or container replacement are required.

Record the advisory link and package evidence. A version string alone may not establish patch status when a distributor supplies backported fixes.

3. Assign patch ownership before work starts

A PHP security checklist needs accountable people, not just technical tasks. The website developer may manage application code while the hosting company controls PHP packages. Your IT provider may manage neither unless that responsibility is explicitly included.

For every affected service, name a business owner who can approve disruption, a technical owner who will apply the fix, and a tester who understands the application’s important workflows.

Send providers a specific request:

> Please confirm whether this service is affected by the PHP advisories, which runtime and package it uses, the applicable fixed build, your deployment timing, and the evidence you will provide after installation and restart.

For managed hosting, ask whether the provider updates the runtime automatically or requires a control-panel change. For vendor appliances, request a supported firmware or product update; do not manually replace embedded PHP unless the vendor directs you to do so.

For containers, update the source image and deployment configuration as well as running instances. Otherwise, a later redeployment could restore vulnerable software.

4. Prioritise exposure and control unavoidable delays

Address affected internet-facing services first, especially those handling payments, customer information or privileged administration. Internal services also need assessment: restricted access reduces exposure but does not repair vulnerable software.

If a fix cannot be applied promptly, ask the technical owner to assess official temporary guidance. Options may include restricting access, disabling an affected service or temporarily withdrawing it from public use. Each choice needs an owner, an expiry time and a clear statement of business impact.

Do not assume a web application firewall, login page or content delivery network makes an unpatched runtime safe. Temporary controls should be documented as risk reduction, not as equivalent to patching.

If interruption is likely, use your downtime costs and recovery priorities to decide which transactions need an alternative process. Customer communications and manual order handling should be agreed before a service goes offline where circumstances allow.

5. Patch the runtime and test business workflows

Before deployment, confirm that you have a usable backup of relevant application files, configuration and data. Document the recovery process and who can authorise it. Restoring an older vulnerable runtime is not a safe long-term rollback strategy.

Use staging to check compatibility where available, without allowing an open-ended test cycle to postpone an urgent security fix. Apply the supported update, then restart or replace the relevant processes as directed by the vendor. An updated package on disk does not necessarily mean existing workers are using it.

Your post-update PHP security checklist should cover:

  • Runtime verification: confirm the serving process uses the intended fixed build across every node or replica.
  • Customer journeys: test sign-in, search, forms, uploads, bookings and checkout where relevant.
  • Integrations: check payment callbacks, API connections, scheduled jobs and transactional email.
  • Data integrity: confirm transactions are recorded once and reach the correct downstream system.
  • Operational health: review application errors, worker restarts, response times and resource use against normal behaviour.

Use approved test accounts and transactions. Record who tested each workflow and the outcome. A working homepage is not sufficient evidence that the application is healthy.

6. Check for compromise and keep closure evidence

Patching removes the addressed weakness; it does not establish that nobody exploited it earlier. Preserve available web, application, operating system and security logs, and review the relevant exposure period with your security team.

Investigate unexpected executable files, unfamiliar administrative accounts, unusual child processes from web workers, unexplained outbound connections and suspicious configuration changes. These are investigation leads, not proof of either reported vulnerability being exploited.

If compromise is suspected, preserve evidence and follow an incident response process rather than simply reinstalling packages and deleting suspicious files. Our first-24-hours ransomware response guide provides related guidance on containment and coordination if ransomware activity is also involved.

Close each register entry only when it contains the applicable advisory, fixed package evidence, deployment time, serving-runtime confirmation, test results and any outstanding investigation. Record exceptions with an accountable owner and review date.

Turn the response into a repeatable security process

The useful outcome is more than an updated website. It is a reliable record of where PHP runs, who maintains it and how the business verifies urgent changes.

Tech Engine can help review your cyber security, clarify managed IT responsibilities and coordinate remediation with hosting and development teams. Contact sales@techengine.au or call 1300 088 324 to review your exposure and response process.

Want this applied to your business?

Request an AI Blueprint and we will map the processes worth automating first.

Request an AI Blueprint