Like zEitEr said, if you open the patch file, you will see it has patches for both.Thanks, can you confirm that both 109618 and 109619 have been patched, since the filename only references 618?
Like zEitEr said, if you open the patch file, you will see it has patches for both.Thanks, can you confirm that both 109618 and 109619 have been patched, since the filename only references 618?
There is no way to upgrade PHP. How to solve it temporarily?
If rebuilding isn't possible right now: our open-source extension mirrors the official fix on an unpatched PHP 5.4–8.5 without recompiling PHP. There's a prebuilt x86_64/arm64 .so per PHP version: copy it into that version's extension_dir (/usr/local/phpXY/bin/php -n -r 'echo PHP_EXTENSION_DIR;'), add a 20-hp_uploadprogress_guard.ini with extension=hp_uploadprogress_guard.so to /usr/local/phpXY/lib/php.conf.d/, restart PHP and check with /usr/local/phpXY/bin/php --ri hp_uploadprogress_guard. It steps aside by itself once a patched PHP is built.There is no way to upgrade PHP. How to solve it temporarily?
da build php as described above remains the real fix.It looks very cool.If rebuilding isn't possible right now: our open-source extension mirrors the official fix on an unpatched PHP 5.4–8.5 without recompiling PHP. There's a prebuilt x86_64/arm64 .so per PHP version: copy it into that version's extension_dir (/usr/local/phpXY/bin/php -n -r 'echo PHP_EXTENSION_DIR;'), add a 20-hp_uploadprogress_guard.ini with extension=hp_uploadprogress_guard.so to /usr/local/phpXY/lib/php.conf.d/, restart PHP and check with /usr/local/phpXY/bin/php --ri hp_uploadprogress_guard. It steps aside by itself once a patched PHP is built.
Honest caveat: we haven't tested it under lsphp ourselves, so please do a test upload after installing.da build phpas described above remains the real fix.
![]()
GitHub - HOSTED-POWER/php_uploadprogress_guard: Protects an unpatched PHP against php2shell (CVE-2026-109618 / CVE-2026-109619): a small extension that mirrors the official fix component by component and steps aside once the engine carries it. PHP 5.
Protects an unpatched PHP against php2shell (CVE-2026-109618 / CVE-2026-109619): a small extension that mirrors the official fix component by component and steps aside once the engine carries it. P...github.com
Sir The last PHP bug need to fixNobody knows what customisation you have. So we can not guide you on a way to save the customisation. Regular servers will get updated with the command:
Code:da update da build php
and if you used an official way to customize software/installation the suggested commands should not remove the customisation.
Curious that PHP8.1 is in the list (or maybe not) as PHP8.1 also got an update during the initial DA patch release yesterday.First make sure you see patches for 5.6 and 7.2. using the command:
Bash:ls -la /usr/local/directadmin/custombuild/patches/php-*/*-cve-2026-10961?.patch
Expected output:
Bash:-rw-r--r-- 1 root root 19603 Oct 21 20:34 /usr/local/directadmin/custombuild/patches/php-5.6/173-php-5.6-cve-2026-109618.patch -rw-r--r-- 1 root root 28416 Oct 21 20:34 /usr/local/directadmin/custombuild/patches/php-7.0/184-php-7.0-cve-2026-109618.patch -rw-r--r-- 1 root root 28296 Oct 21 20:34 /usr/local/directadmin/custombuild/patches/php-7.1/186-php-7.1-cve-2026-109618.patch -rw-r--r-- 1 root root 38460 Oct 21 20:34 /usr/local/directadmin/custombuild/patches/php-7.2/159-php-7.2-cve-2026-109618.patch -rw-r--r-- 1 root root 38329 Oct 21 20:34 /usr/local/directadmin/custombuild/patches/php-7.3/139-php-7.3-cve-2026-109618.patch -rw-r--r-- 1 root root 40315 Oct 21 20:34 /usr/local/directadmin/custombuild/patches/php-7.4/143-php-7.4-cve-2026-109618.patch -rw-r--r-- 1 root root 40650 Oct 21 20:34 /usr/local/directadmin/custombuild/patches/php-8.0/138-php-8.0-cve-2026-109618.patch -rw-r--r-- 1 root root 49737 Oct 21 20:34 /usr/local/directadmin/custombuild/patches/php-8.1/114-php-8.1-cve-2026-109618.patch
Then check
Code:da build versions | grep avail
whether or not updates for PHP are offered.
If you see patches and no updates are available, then you are most likely secured.
Can it be run on CentOS 6?If rebuilding isn't possible right now: our open-source extension mirrors the official fix on an unpatched PHP 5.4–8.5 without recompiling PHP. There's a prebuilt x86_64/arm64 .so per PHP version: copy it into that version's extension_dir (/usr/local/phpXY/bin/php -n -r 'echo PHP_EXTENSION_DIR;'), add a 20-hp_uploadprogress_guard.ini with extension=hp_uploadprogress_guard.so to /usr/local/phpXY/lib/php.conf.d/, restart PHP and check with /usr/local/phpXY/bin/php --ri hp_uploadprogress_guard. It steps aside by itself once a patched PHP is built.
Honest caveat: we haven't tested it under lsphp ourselves, so please do a test upload after installing.da build phpas described above remains the real fix.
![]()
GitHub - HOSTED-POWER/php_uploadprogress_guard: Protects an unpatched PHP against php2shell (CVE-2026-109618 / CVE-2026-109619): a small extension that mirrors the official fix component by component and steps aside once the engine carries it. PHP 5.
Protects an unpatched PHP against php2shell (CVE-2026-109618 / CVE-2026-109619): a small extension that mirrors the official fix component by component and steps aside once the engine carries it. P...github.com
If you can not upgrade PHP, then please follow official instructions from PHP maintainers - https://www.php.net/archive/2026.php#2026-10-21-5There is no way to upgrade PHP. How to solve it temporarily?