WordPress 7.1.4: update your live site.

List the production installation, any other live copies and the person responsible for each. Confirm a recoverable database and file backup, then use the normal update or deployment route for that site. WordPress documents both dashboard and background updates. Check the installed version afterwards instead of assuming an automatic update finished.

A staging copy helps developers check custom themes, plugins and integrations before the live release. Keep that test focused: a security patch should not wait for an unrelated redesign or a major feature upgrade. Record a short acceptance list and who can approve the result.

Exercise forms, account access, uploads and any checkout or booking flow. Confirm that submissions reach the intended system and that background jobs still run. Check application and web-server errors after the release, then clear relevant caches and test the public pages again.

Updating core and investigating a suspicious site are separate tasks. Unexpected administrator accounts, changed application files, injected scripts or unexplained outbound requests warrant investigation even after the version number is current. Preserve relevant logs and compare files against the expected release before replacing evidence.

Ask your hosting and development teams to agree who checks the application, server and access history. A restored page is only one part of acceptance. Test the business workflows and establish whether credentials or integrations need attention when an investigation finds unauthorized access.

A firewall can help restrict unwanted traffic, but the security release still needs installing. Keep temporary controls, the core update and any incident investigation recorded as separate actions, with an owner for each.

Intercube engineers operate the managed runtime, web services and infrastructure behind your WordPress application. Your developers own the application and plugin decisions, with engineering support from people who understand the hosting and release route. A separate preview or staging environment gives both teams somewhere to test an update together.

Build and deployment pipelines are included in the managed hosting plan. Your team can release repository-managed code through Intercube without setting up a separate GitHub Actions deployment workflow or paying a separate CI runner bill for that pipeline. Keeping the build and production configuration connected makes the next update easier to repeat.

If your current host leaves infrastructure maintenance and release problems with your developers, this is a useful time to move. Intercube prepares the target environment and agrees the application checks and cutover with your team. Migration to Intercube managed hosting is included at no additional cost.