No public statement located for Sage 300 CRE as of 23 October 2026, 00:19 UTC; places checked: search:Sage 300 CRE PHP2Shell; search:Sage PHP2Shell CVE-2026-109618; search:Sage security advisories trust center PHP October 2026; https://www.sage.com/en-us/trust-and-security/ (fetch failed, client error); https://www.sage.com/en-gb/trust-and-security/ (fetch failed, client error); https://www.sage.com/en-us/trust-and-security/security/ (fetch failed, client error); https://www.sage.com/en-us/news/press-releases/; https://status.sage.com/; https://www.sage.com/en-us/blog/.
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:Sage 300 CRE PHP2Shell; search:Sage PHP2Shell CVE-2026-109618; search:Sage security advisories trust center PHP October 2026; https://www.sage.com/en-us/trust-and-security/ (fetch failed, client error); https://www.sage.com/en-gb/trust-and-security/ (fetch failed, client error); https://www.sage.com/en-us/trust-and-security/security/ (fetch failed, client error); https://www.sage.com/en-us/news/press-releases/; https://status.sage.com/; https://www.sage.com/en-us/blog/.
Notes
Sage trust and security hub blocked the fetch; press releases newest 1 Oct 2026; status.sage.com shows only availability incidents 21 to 22 Oct 2026 with no PHP or security wording; blog newest 2 Oct 2026.
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 Sage 300 CRE and PHP2Shell
Is Sage 300 CRE affected by PHP2Shell?
No public statement located for Sage 300 CRE as of 23 October 2026, 00:19 UTC; places checked: search:Sage 300 CRE PHP2Shell; search:Sage PHP2Shell CVE-2026-109618; search:Sage security advisories trust center PHP October 2026; https://www.sage.com/en-us/trust-and-security/ (fetch failed, client error); https://www.sage.com/en-gb/trust-and-security/ (fetch failed, client error); https://www.sage.com/en-us/trust-and-security/security/ (fetch failed, client error); https://www.sage.com/en-us/news/press-releases/; https://status.sage.com/; https://www.sage.com/en-us/blog/.
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.