Daily · Article 02 · 3 min read
- Security
- Open source
Cloudways reports PHP patches applied to all active servers on both plans
Cloudways rollout completion report · November 21, 05:10 JST
Summary
Cloudways reported at 05:10 JST on November 21 that it had patched all active Flexible and Autonomous servers. Here is what to check for a specific site.
Key facts
Cloudways, a provider that manages servers for websites, said at 05:10 JST on November 21 (20:10 UTC on November 20) that it had applied PHP security patches to all active servers on both plans. It said customers needed no further action and monitoring would continue. At 16:29 JST the previous day, the provider had reported completion for active Autonomous apps and work still outstanding on Flexible. Cloudways update

1. The supplier’s release and the site running it
PHP is the runtime websites such as WordPress use to build pages on a server. The PHP team published fixes for supported branches on November 19. Cloudways started rolling them out to its managed servers, and Japan’s Information-technology Promotion Agency (IPA) issued guidance on November 20. The exact application time for a site is evidence held by its operator.
| Owner and stage | Confirmed status | How to match your deployment |
|---|---|---|
| Fix published · PHP team | Confirmed releases 8.2.36, 8.3.37, 8.4.28 and 8.5.13 | Match your branch to the PHP changelog |
| Rollout and application · Cloudways Autonomous | Provider reports all active servers patched | Match the plan and active app to the provider update |
| Rollout and application · Cloudways Flexible | Provider reports all active servers patched, completing the remaining work from its earlier update | Check the server’s patch record alongside the provider update |
| Live deployment check · site operator | Each site's active build and application time are unverified in the public notice | Identify the app and environment, then confirm the running PHP build and patch time |
- Owner and stage
Fix published · PHP team
- Confirmed status
- Confirmed releases 8.2.36, 8.3.37, 8.4.28 and 8.5.13
- How to match your deployment
- Match your branch to the PHP changelog
- Owner and stage
Rollout and application · Cloudways Autonomous
- Confirmed status
- Provider reports all active servers patched
- How to match your deployment
- Match the plan and active app to the provider update
- Owner and stage
Rollout and application · Cloudways Flexible
- Confirmed status
- Provider reports all active servers patched, completing the remaining work from its earlier update
- How to match your deployment
- Check the server’s patch record alongside the provider update
- Owner and stage
Live deployment check · site operator
- Confirmed status
- Each site's active build and application time are unverified in the public notice
- How to match your deployment
- Identify the app and environment, then confirm the running PHP build and patch time
The cat asks Q&A
- The researcher
The update is out. Has my service received it?
Pocket NotebookFor both plans, the completion report covers active servers. Identify the environment processing your site’s requests. If you need evidence, ask support for that environment’s running PHP build and the time it was patched.
2. Different responsibilities within the same team
Imagine a team runs its production site on Autonomous and a separate staging site on Flexible. It can check each environment against the provider’s active-server coverage. If the team also operates its own Amazon Linux 2023 environment, it must apply the update there and verify the running service.
| Hypothetical deployment | What to check or do |
|---|---|
| A Cloudways Autonomous app | Identify the plan and active app in the dashboard. Ask support for the running build and application time if needed |
| A Cloudways Flexible server | Check that the staging server was active and covered. Use its server-specific patch record if evidence is needed |
| Self-managed Amazon Linux 2023 | Match the package and branch to the AWS advisory. Verify the PHP service restart or replacement image after installation |
- Hypothetical deployment
A Cloudways Autonomous app
- What to check or do
- Identify the plan and active app in the dashboard. Ask support for the running build and application time if needed
- Hypothetical deployment
A Cloudways Flexible server
- What to check or do
- Check that the staging server was active and covered. Use its server-specific patch record if evidence is needed
- Hypothetical deployment
Self-managed Amazon Linux 2023
- What to check or do
- Match the package and branch to the AWS advisory. Verify the PHP service restart or replacement image after installation
The cat asks Q&A
- The researcher
The WordPress dashboard says it is up to date. Is that enough?
Pocket NotebookThe dashboard shows the application version. This patch calls for checking which PHP build handles page requests.
To close
Use the actual site name when confirming the update
When asking a provider, give the service name, plan and server or environment and ask for the patched PHP build and application time. The status page reports the provider’s rollout scope. It does not establish whether a particular site was exploited. IPA response guidance
Sources
- provider updatestatus.cloudways.com
- PHP changelogphp.net
- AWS advisoryaws.amazon.com
- IPA response guidanceipa.go.jp