{"id":16242,"date":"2026-10-22T05:11:14","date_gmt":"2026-10-21T20:11:14","guid":{"rendered":"https:\/\/hanami-web.tokyo.jp\/blog\/?p=16242"},"modified":"2026-10-23T04:45:09","modified_gmt":"2026-10-22T19:45:09","slug":"php2026-wordpress","status":"publish","type":"post","link":"https:\/\/hanami-web.tokyo.jp\/blog\/en\/website-running\/security-case\/php2026-wordpress\/","title":{"rendered":"Summary of how to address critical PHP vulnerabilities on WordPress sites."},"content":{"rendered":"

This is misa from HanamiWEB.
Due to the critical vulnerability in PHP announced on October 21, 2026, we have received many inquiries since yesterday.<\/p>\n\n\n\n

WordPress uses PHP, so it is a target application.
There's a lot of information circulating about needing to upgrade the PHP version or apply patches, and I imagine many people are feeling very anxious about what to do. For example, with Xserver, as of October 21, 2022, it's currently impossible to log in to the server.
Upgrading the PHP version requires logging into the server, so the conclusion is that it was impossible to access PHP at that time.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

As of October 22, 2026, it's now possible to log in to the admin panel, so we'd like to share the steps we took to address the issue on the WordPress sites we manage!<\/p>\n\n\n\n

<\/p>\n\n\n\n

\n
\n

table of contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n