No public statement located as of 23 October 2026.
This index reports published statements and AI answers on stated dates. It is not a security assessment. For patching, follow PHP's advisory and your host.
search:WHMCS PHP2Shell (web search budget exhausted in this run)
Last checked
The statement
No public statement located as of at: https://blog.whmcs.com/ (newest posts WHMCS 9.1 and maintenance releases, no dates printed, nothing on PHP2Shell); https://github.com/NCSC-NL/php2shell (software list, status update 23 October 2026 00:48 CEST) (WHMCS self-hosted application listed Vulnerable citing system requirements only); search:WHMCS PHP2Shell (web search budget exhausted in this run).
Notes
No WHMCS statement on PHP2Shell found on its blog as of the last check. NCSC-NL inventory lists the WHMCS self-hosted application as Vulnerable on the basis of its PHP system requirements, not a vendor statement.
Change log
: first check
What the five engines said
AI answers not yet measured
Submit a correction or your statement
Submit a correction or your statement. We list a statement only once we have opened it on your own domain or verified official account. Disputes follow the dispute policy. Or email the statement link to index@broadcastwell.com.
Badge
A badge is issued once a public statement is located and verified on the company's own domain or verified official account.
WHMCS's customers can ask us for the PHP2Shell Record Check: we capture what ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode say about WHMCS and PHP2Shell, trace every wrong or missing statement to its source and deliver a statement page in the format the engines quote. Record Check $490 once.
About this page
This index reports published statements and AI answers on stated dates. It is not a security assessment. For patching, follow PHP's advisory and your host.