Official source: WordPress 7.1.4 release announcement
Should a business update to WordPress 7.1.4?
Yes. WordPress released version 7.1.4 on 28 October as a security update and recommends updating sites immediately. For a business website, “immediately” means prioritise it ahead of routine improvements—not skipping the safeguards that protect orders, enquiries and essential content.
Our judgement is simple: move quickly, but do not turn the live site into an unchecked deployment. Confirm there is a usable backup, agree who owns the update, apply the smallest safe change, then test the customer journeys that matter. That is a calmer route than either postponing a security release or clicking update with nobody accountable for the outcome.
What did WordPress report?
The official announcement describes 7.1.4 as a security release with fixes for multiple issues. It includes a weakness in the upgrade process that could lead to remote code execution during an upgrade window, several stored cross-site scripting issues, an information-disclosure issue involving unpublished Customizer changesets, and an update to bundled root certificates.
Those are WordPress’s reported release facts, not evidence that any particular Jenlu client site has been affected. The relevant decision for an owner is whether the site is on an eligible WordPress branch, who can safely apply its update, and whether the business has a way to confirm the site still works afterwards.
A controlled update plan for a live site
- Check the installed version and ownership. Identify the live WordPress version and the person or support partner responsible for the update. Do not assume automatic updates completed successfully.
- Take and verify a recoverable backup. Record where the files and database backup are held, when they were made and how restoration would be requested. A backup that cannot be found or restored is not a dependable fallback.
- Choose a sensible window. For a brochure site, this may be a short, quiet period. For ecommerce, bookings, memberships or regulated journeys, plan around transactions, integrations and customer communications.
- Update the smallest necessary scope. Apply the WordPress core security update. Separate unrelated plugin, theme or content changes so that any issue is easier to isolate.
- Keep a brief record. Note the version before and after, the time of change, who made it and the checks completed. This makes a later support request much faster to triage.
What should be checked after the update?
Start with the journeys through which the business earns, serves or hears from customers: the homepage, contact form and email notification; logins; search; booking or checkout; and any important payment, CRM or analytics hand-off. Also look at the site on a phone, because a working desktop page does not prove the responsive journey is intact.
If the site handles personal data, payments or high-value enquiries, decide in advance who is told if a test fails and how the change would be rolled back. That preparation is part of responsible maintenance, not an optional extra.
A security update deserves urgency. The outcome still needs a deliberate handover: update, check the business-critical route, and record what happened.
Relevant Jenlu service: Jenlu provides WordPress support and care plans for businesses that need updates managed with clear ownership, practical testing and a concise handover.