Microsoft Dynamics 365 and PHP2Shell

Is this your company?

Publish or update your statement. The statement submission is free.

See what ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode say about you: the $490 PHP2Shell Record Check.

We capture the dated answers, trace wrong or missing statements to their sources and deliver a statement page in the format the engines quote.

Agencies: white-label PHP2Shell Record Check, $490 per client report.

The statement

No public statement located as of 23 October 2026, 02:03 UTC at: https://techcommunity.microsoft.com/blog/azurenetworksecurityblog/addressing-php2shell-cve-2026-109618-and-cve-2026-109619-upgrade-guidance-and-az/4566623; search:Microsoft PHP2Shell; https://techcommunity.microsoft.com/blog/azurenetworksecurityblog/addressing-php2shell-cve-2026-109618-and-cve-2026-109619-upgrade-guidance-and-az/4566623 (Azure Network Security Blog post, body renders by script, only title and opening read); https://msrc.microsoft.com/blog/ (302 redirect to https://www.microsoft.com/en-us/msrc/blog, no PHP post); https://azure.status.microsoft/en-us/status/history/ (Azure status history, no entries dated 20 to 23 October 2026, no PHP mention).

Notes

Microsoft published a Tech Community post on PHP2Shell upgrade guidance and Azure WAF mitigations (page metadata modified 2026-10-22) at https://techcommunity.microsoft.com/blog/azurenetworksecurityblog/addressing-php2shell-cve-2026-109618-and-cve-2026-109619-upgrade-guidance-and-az/4566623; it is customer guidance for Azure workloads and says nothing specific to Dynamics 365, so no Dynamics 365 statement is recorded. The post body loads by script and was not read in full. Post titled Addressing PHP2Shell CVE-2026-109618 and CVE-2026-109619: upgrade guidance and Azure WAF mitigations on Microsoft's Tech Community; readable opening: Today, two critical remote code execution (RCE) vulnerabilities were disclosed in PHP. quoted from the statement URL. Only the title and opening could be read (body loads by script), so the status rests on the title's own words (Azure WAF mitigations plus customer upgrade guidance) and should be rechecked in a full read. No date printed; page metadata modified_time 2026-10-22T10:26:20-07:00. Nothing found specific to Dynamics 365. 23 October source review: new Azure WAF guidance is product-specific to Azure and does not establish Dynamics 365 status. No cross-product inference applied.

Change log

• 23 October 2026: first check

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 Microsoft Dynamics 365 and PHP2Shell

Is Microsoft Dynamics 365 affected by PHP2Shell?

No public statement located for Microsoft Dynamics 365 as of 23 October 2026, 02:03 UTC; places checked: https://techcommunity.microsoft.com/blog/azurenetworksecurityblog/addressing-php2shell-cve-2026-109618-and-cve-2026-109619-upgrade-guidance-and-az/4566623; search:Microsoft PHP2Shell; https://techcommunity.microsoft.com/blog/azurenetworksecurityblog/addressing-php2shell-cve-2026-109618-and-cve-2026-109619-upgrade-guidance-and-az/4566623 (Azure Network Security Blog post, body renders by script, only title and opening read); https://msrc.microsoft.com/blog/ (302 redirect to https://www.microsoft.com/en-us/msrc/blog, no PHP post); https://azure.status.microsoft/en-us/status/history/ (Azure status history, no entries dated 20 to 23 October 2026, no PHP mention).

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.