Official source: WordPress 7.0.4 release
On 12 August, WordPress published version 7.0.4 with a security fix and advised site owners to update. The release addresses an authenticated Author+ remote-code-execution issue involving malicious file upload on sites that use Imagick and Ghostscript. That is a strong reminder that routine maintenance is part of protecting a website, its enquiries and its reputation.
“Update immediately” does not have to mean “update blindly”. A good maintenance route makes the decision quick and deliberate: confirm a recoverable backup, understand whether the site has custom functionality, apply the update in the appropriate environment, then check the customer journeys that keep the business moving.
Security releases deserve urgency. A dependable process makes that urgency manageable rather than disruptive.
What to check after a security update
- Confirm the update completed successfully and the site is showing the intended version.
- Test the routes customers rely on, including contact forms, logins, booking, checkout and confirmation emails.
- Check error logs and key integrations where the site uses bespoke code or third-party services.
- Record what changed, when it changed and how to restore a known working version if needed.
When support is worth having
Businesses with an inherited website, a busy ecommerce journey or compliance-sensitive content cannot afford uncertainty around maintenance. A support partner can establish the update routine, identify what needs testing and give you a clear route for action when a security release appears.
Relevant Jenlu service: Jenlu helps businesses take ownership of WordPress maintenance, assess update risk and keep key customer journeys working.