No public statement located for MerusCase as of 23 October 2026, 17:27 UTC; places checked: search:MerusCase PHP2Shell; https://www.meruscase.com/; https://legal.meruscase.com/vulnerability-reporting-policy; http://blog.meruscase.com (newest post January 31, 2023).
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:MerusCase PHP2Shell; https://www.meruscase.com/; https://legal.meruscase.com/vulnerability-reporting-policy; http://blog.meruscase.com (newest post January 31, 2023).
Notes
No status page or newsroom linked from the homepage. Vulnerability Reporting Policy page is a generic researcher policy with no advisory content.
Change log
: first check
: Source-only recheck completed; published classification unchanged.
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 MerusCase and PHP2Shell
Is MerusCase affected by PHP2Shell?
No public statement located for MerusCase as of 23 October 2026, 17:27 UTC; places checked: search:MerusCase PHP2Shell; https://www.meruscase.com/; https://legal.meruscase.com/vulnerability-reporting-policy; http://blog.meruscase.com (newest post January 31, 2023).
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.