WEBSITE SECURITY

Critical PHP Security Update: What It Means for Your Website

A note for TradeBark clients

TradeBark-managed websites are up to date on PHP. We’re also checking hosting platforms against today’s security advisories and coordinating any additional updates needed.

OCTOBER 21, 2026 SECURITY UPDATE

A serious alert.

Critical PHP vulnerabilities have prompted urgent security updates. Website owners should verify that their hosting providers have applied the necessary patches.

Security fixes are available.
SECURITY RELEASEPHP2Shell
Two critical vulnerabilitiesPHP updates released

Your website depends on more than what visitors see.

A website relies on software working behind the scenes. On October 21, the PHP project issued emergency security releases for two critical vulnerabilities, widely referred to as PHP2Shell.

The issue deserves prompt attention. It also deserves a clear explanation of what is affected, what needs updating, and who is responsible for that work.

WHAT HAPPENED?

Two vulnerabilities.
One urgent priority.

The flaws, tracked as CVE-2026-109618 and CVE-2026-109619, can allow an attacker to run code on an affected server without logging in. PHP’s security team is urging users to update immediately.

Read the PHP project’s October 21 security advisory ↗

An important distinction

A vulnerability is a weakness that needs to be fixed. A security alert does not, by itself, establish that a particular website has been compromised.

WHAT ABOUT WORDPRESS?

The update belongs
in your hosting environment.

PHP helps run WordPress and many other website platforms. WordPress’s own security notice confirms that this issue is in PHP, rather than WordPress itself. No WordPress release is planned to fix these PHP vulnerabilities.

That means clicking “Update” on a plugin or theme won’t resolve this specific problem. Your hosting provider or server administrator needs to confirm the PHP security update.

Read WordPress’s guidance for website owners ↗

THE FIXES HAVE BEEN RELEASED

The PHP releases
that address these flaws.

The PHP project published these fixed releases on October 21:

PHP 8.28.2.35
PHP 8.38.3.36
PHP 8.48.4.27
PHP 8.58.5.12

Some hosting vendors apply security fixes to their own packages without changing the displayed version in the same way. Ask your provider to confirm the fix for both CVEs. PHP 8.1 and older no longer receive routine security releases from the PHP project.

Firewall rules may reduce exposure, but PHP’s maintainers say an update is the complete solution. If a server cannot be patched promptly, its operator should follow the official remediation guidance on restricting exposure.

OUR RESPONSE AT TRADEBARK

Current PHP.
Additional checks underway.

Our managed websites are up to date on PHP. We’re checking their hosting platforms against the latest advisory as an additional verification step and coordinating any further updates that may be required.

That distinction matters: keeping software current is an ongoing responsibility, and a new security release calls for another check. We want our clients to have a clear picture of the situation.

If we manage your website and you have a question, contact our team. We can help you understand the status of your specific project.

YOUR NEXT STEPS

Start with the team
responsible for your hosting.

  1. Ask for confirmation.

    Ask your hosting provider whether your website’s PHP installation has been patched for CVE-2026-109618 and CVE-2026-109619. Request confirmation for your environment, rather than relying on a general service announcement.

  2. Coordinate the update and follow-up.

    Have your hosting team apply the appropriate security update promptly. As part of the work, confirm backup availability and check important functions such as forms, checkout, and account access.

  3. Raise any unusual behavior.

    If you notice unexpected changes or receive a security alert, tell your hosting or support team. Patching a vulnerability and investigating a possible compromise are separate tasks.

Sources & further reading

Information checked October 21, 2026. This is a developing security issue; consult the linked advisories and your hosting provider for current guidance and the status of your own environment.