No public statement located for InEight as of 23 October 2026, 00:22 UTC; places checked: search:InEight PHP2Shell; https://ineight.com/security/ (fetch failed, client error); https://ineight.com/; https://ineight.com/company/security/; https://ineight.com/news/.
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.
No public statement located as of at: search:InEight PHP2Shell; https://ineight.com/security/ (fetch failed, client error); https://ineight.com/; https://ineight.com/company/security/; https://ineight.com/news/.
Notes
Security page has no PHP mention; newsroom shows undated customer and FedRAMP items, none about PHP; no status page link in site navigation.
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.
Questions about InEight and PHP2Shell
Is InEight affected by PHP2Shell?
No public statement located for InEight as of 23 October 2026, 00:22 UTC; places checked: search:InEight PHP2Shell; https://ineight.com/security/ (fetch failed, client error); https://ineight.com/; https://ineight.com/company/security/; https://ineight.com/news/.
The status records what the company published, under our statement status rules. A PHP version mentioned in a statement can be guidance for other organisations; the statement and notes explain its scope.
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.