Products and stacks · CMS and web applications

PHP2Shell in Joomla: is it affected and how to fix it

How to check the PHP version Joomla uses

Run the command for your setup. A version at or above 8.2.35, 8.3.36, 8.4.27 or 8.5.12 in its branch is fixed; older branches are fixed only by a vendor build that says so.

php -v
<?php phpinfo(); // temporary, behind authentication, delete afterwards

The command-line php can differ from the PHP that serves the site. To be sure, check the web SAPI (a temporary phpinfo() page behind authentication, or the panel's PHP settings) and remove it afterwards. Our version checker compares a version number for you.

🔎 Got a version number? Paste it into the PHP2Shell checker →

How to fix PHP2Shell in Joomla

Find out where the PHP that runs this application comes from: your distribution, a third-party repository (Ondřej Surý, Remi), a hosting panel, a Docker image or your host.
Update that PHP to 8.2.35, 8.3.36, 8.4.27, 8.5.12 or a vendor build with the backported fix, and restart every PHP worker.
On shared or managed hosting you cannot patch PHP yourself: ask the host whether the fixed PHP is deployed, and switch the site to a fixed version in the panel.
If the site still runs PHP 8.1 or older, move it to a supported branch; PHP published only source patches for 7.4, 8.0 and 8.1.

Prefer to let an AI agent do the checks? Check if you are affected · Fix with an AI agent

If you cannot patch yet

Set session.upload_progress.enabled = 0 where applications cannot override it (php.ini, php_admin_value in the FPM pool or Apache config), and restart PHP.
On PHP 8.5, set fatal_error_backtraces = 0.
PHP's interim advice also covers memory_limit and a low post_max_size; follow the remediation page exactly, because these settings only reduce some paths.
Restrict access (VPN, IP allowlist) or take the service offline if it runs PHP 8.1 or older with no vendor backport. WAF rules help but are not a fix.

FAQ

Is Joomla affected by PHP2Shell?

Affected if the PHP underneath is older than the fixed releases. The flaw is in the PHP interpreter, not in this application. Updating the application or its plugins does not fix it; the PHP that serves it must be patched. We found no product-specific PHP2Shell statement from the vendor as of the check date. This release line is end of life and old versions often cannot run on PHP 8.2 or newer; check the application's own requirements before switching PHP, and plan a migration. The Docker Official Image for this application was rebuilt with fixed PHP on 21 October; pull it and redeploy.

Does updating Joomla itself fix CVE-2026-109618 and CVE-2026-109619?

Only if the update contains fixed PHP. PHP2Shell is a flaw in the PHP interpreter, so what matters is the PHP that Joomla runs on. Check the version after updating.

Which PHP versions fix PHP2Shell?

PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12, released 21 October 2026. PHP 8.1 and older get no release from the PHP project; only vendor builds with a backport (or a self-built source patch for 7.4, 8.0 and 8.1) fix them.

What if Joomla has no fix yet?

Keep its PHP-based web interface off the internet (VPN or IP allowlist), apply PHP's interim settings such as disabling session upload progress, and install the vendor update as soon as it ships. Interim settings reduce risk but are not a fix.

← All products that bundle PHP

Sources

Outbound links leave this site. We do not host exploit code.

Unofficial summary of public sources. This site is not affiliated with the vendor or the PHP project and hosts no exploit code.