Official source: WordPress 7.1.2 Release
WordPress released version 7.1.2 on 22 September with a fix for a critical-severity security vulnerability. WordPress recommends updating sites immediately. The issue can allow an unauthenticated attacker, under particular server and theme conditions, to read a chosen local PHP file and potentially achieve remote code execution.
That description is deliberately technical. For a business, the practical message is simple: do not leave an update of this kind sitting in a dashboard without a named owner and a sensible checking route.
A security update is not complete when a button is pressed. It is complete when the website is current and the customer journeys it supports have been checked.
Start with the sites that matter most
Prioritise any WordPress site that collects enquiries, accepts orders, handles account information, supports regulated services or gives staff access to business systems. If automatic background updates are enabled, confirm the installed version rather than assuming the change has applied successfully.
For sites with custom themes, integrations or a history of plugin conflicts, take an available backup first and use a staging environment where practical. A short, controlled update is generally safer than either rushing a complex site blindly or postponing a critical release indefinitely.
Four checks after updating
- Confirm the version. Check that WordPress 7.1.2 is installed and that the update did not report errors or leave pending database work.
- Test the journey that makes the site valuable. Submit a contact form, place a test order where appropriate, try a booking or login route, and check the confirmation message or email that follows.
- Review the visible basics. Open key pages on desktop and mobile, then check navigation, images, search, cookie tools and any important third-party integration.
- Record ownership. Note who updated the site, when it was checked and what would happen if a problem emerged. This is especially useful when a site has several suppliers or internal contributors.
Security is also a continuity question
The update itself is important, but it also exposes whether a website has dependable technical ownership. A current backup, known hosting access, a clear update rhythm and a tested route for forms, sales or customer service turn a security response into routine maintenance rather than an urgent scramble.
WordPress has backported this fix to branches eligible for security fixes, but the project also notes that only the latest release is actively supported. That is a useful prompt to understand what version a business is running and who is responsible for keeping it current.
Relevant Jenlu service: Jenlu provides practical WordPress support for updates, fixes, hosting coordination and the business-critical checks that keep a website dependable.