Official source: WordPress 7.1.1 Maintenance and Security Release
WordPress released version 7.1.1 on 17 September. It includes 17 Core bug fixes, 19 Block Editor bug fixes and 11 security fixes. WordPress recommends updating sites immediately; it also says the fixes are being backported where necessary to versions that remain eligible for security updates.
That makes this a useful moment to distinguish speed from haste. A business should not leave a security release waiting without a reason, but the update should still have an owner and a short, intentional check afterwards.
A successful update is not simply one that completes. It is one that leaves the website safe and the customer journey working.
A practical update sequence
- Confirm what is being updated. Note the current WordPress version, hosting environment and any essential plugins or integrations. Make sure there is a recent, usable backup before starting.
- Apply the release promptly. Use the normal managed update route, or have a trusted supplier do it. Avoid making unrelated design or plugin changes at the same time; a focused change is easier to check and reverse if needed.
- Test the journeys customers use. Visit key pages in a normal browser, submit the main contact form and test the checkout, booking or sign-in route where relevant. Check the confirmation emails and third-party connections that support those journeys.
- Record the result. Keep a simple note of when the update happened, what was checked and who owns the next review. This makes future support faster, especially if the site is inherited or has several suppliers.
Why older WordPress sites still need attention
WordPress has said that security fixes are being backported where necessary to branches still eligible for them, but only the most recent WordPress version is actively supported. That is a sensible prompt to understand the age and maintenance status of a site rather than assuming every update path is equally safe.
For teams with an older or heavily customised website, the right route may include a staging check or a planned upgrade. The important thing is to avoid the common gap where nobody knows who can act, which credentials are needed, or whether a backup can genuinely restore service.
Relevant Jenlu service: Jenlu provides practical WordPress support for security updates, inherited sites, recovery planning and the customer journeys that need to keep working.