[php-src] Issue #24627: Vendor Build Version field needed, visible in phpinfo()
| From: | JDBushQuacken | Date: | Fri, 23 Oct 2026 23:44:19 +0000 |
| Subject: | [php-src] Issue #24627: Vendor Build Version field needed, visible in phpinfo() | ||
| Groups: | php.bugs | ||
| Request: | Send a blank email to php-bugs+get-253148@lists.php.net to get a copy of this message | ||
Issue: https://github.com/php/php-src/issues/24627
Author: JDBushQuacken
Congratulations on the rapid and successful rollout of the PHP2Shell mitigation.
When vendors updated their builds to include the fixes, some did not update the Version stamps to
reflect the PHP.net version, which created a lot of confusion. I believe that there were thousands
of support calls to hosting providers that could have been avoided if the version stamp reported by
phpinfo() was more complete. For example, CloudLinux created a version containing both CVE fixes,
which still showed up in phpinfo() as 8.5.11. Their internal version nomenclature was not visible,
and everyone had to take their word for it that it contained the fixes. The build date alone did
not offer proof that the CVE fixes were applied. A day or two later, they updated the primary
version stamp to 8.5.12, and issued a statement explaining the process.
It would be beneficial if an item could be added to the phpinfo() output to display the build
version produced by the vendor or hosting provider that updated the code. For example, under the
"Core" section, include "Vendor Build" as a separate item. Then, when another
update blitz like this one occurs again, users would be able to more easily cross reference the full
version number with changelogs or reports issued by their hosting providers. (and not swamp their
hosting provider with unneccessary support calls.)
Thanks for considering,
-JDB