Insights
What Happens When You Don't Update WordPress?
Skipping WordPress updates rarely causes an instant failure. Instead, risk builds quietly until a vulnerability, PHP upgrade or broken plugin forces the issue.
- Published
- Reading time
- 7 min read
WordPress makes updating look simple: a notification appears in the dashboard, a button is clicked and the job is done. Yet a large number of business sites run months or years behind on core, plugin and theme updates. Sometimes this is deliberate – a previous update broke something and nobody wants to risk it again. More often it simply slips down the priority list because the site still appears to work.
The problem is that "still appears to work" says nothing about security, compatibility or how hard the eventual catch-up will be. Not updating WordPress rarely causes an immediate, dramatic failure. Instead, it quietly accumulates risk until a single event – a publicly disclosed vulnerability, a hosting PHP upgrade, a payment gateway change – turns that risk into an outage or a compromise.
This article walks through what actually happens to a WordPress site that is not kept up to date, why updates sometimes break things, and how to update safely.
What a WordPress update actually contains
A typical WordPress site has three layers of software that update independently:
- WordPress core – the CMS itself. Major releases add features and change internals; minor (point) releases are mostly security and bug fixes.
- Plugins – often 15 to 40 on a business site, from forms and SEO tools to page builders and WooCommerce extensions. Each is maintained by a different developer or company on its own schedule.
- Themes – including parent themes and, frequently, bundled page builders or premium plugins distributed with the theme.
Underneath these sit the PHP runtime, the database server (MySQL or MariaDB) and the web server, which are usually managed by the host. Updates at each layer may fix security vulnerabilities, fix bugs, add compatibility with newer PHP versions, or change behaviour that other components depend on.
The security consequences
Known vulnerabilities become public knowledge
When a vulnerability is found in a popular plugin, it is normally fixed in a new release and then disclosed publicly through security advisories and vulnerability databases. From that point, the details of the flaw are available to anyone, including people who build automated scanners. Sites still running the vulnerable version become easy, low-effort targets, and attackers do not need to know or care what your business does – the scanning is indiscriminate.
Abandoned plugins stay vulnerable forever
Plugins are sometimes abandoned by their developers or removed from the WordPress.org directory, occasionally because of an unresolved security issue. If you never review your plugin list, you may be running software that will never receive another fix. Updating is not just about clicking the button; it includes noticing when there is no update to click.
What a compromise looks like
Compromises of outdated WordPress sites typically result in one or more of the following:
- Hidden spam links or pages injected for search engine manipulation.
- Redirects that send mobile or search visitors to scam or malware sites.
- New hidden administrator accounts or backdoor files that allow repeated access.
- Skimming scripts on checkout pages that capture card or personal details.
- The server being used to send spam, leading to email deliverability problems for your whole domain.
The clean-up is usually far more time-consuming than the updates would have been. For warning signs to watch for, read signs your website has been hacked.
The compatibility consequences
Security gets most of the attention, but compatibility problems are just as common and often more disruptive.
PHP version upgrades
Every PHP version has a published end-of-life date. After that date it no longer receives security fixes, and hosting providers eventually upgrade or retire it. Old plugins and themes frequently use functions that have been deprecated or removed in newer PHP versions. A site that has not been updated for years may work perfectly on its current PHP version and then fail with a fatal error the day the host moves it to a supported one. At that point you are no longer choosing when to update; the host has chosen for you.
Plugin interdependencies
Plugins often depend on each other or on specific WordPress core functions. WooCommerce extensions, for example, generally declare which WooCommerce versions they have been tested with. If core moves forward but extensions do not – or the other way round – features may stop working in ways that are hard to diagnose.
Third-party integrations
Payment gateways, shipping providers, CRMs and marketing tools periodically retire older API versions. The plugin that connects your site to them needs updating to keep working. An outdated payment plugin is not just a security risk; it can simply stop taking payments.
The "update debt" problem
Skipping updates creates something similar to technical debt. Each skipped release makes the next update larger and riskier, because more changes need to be applied at once and there are more opportunities for conflicts.
| Update approach | Typical change per update | Risk of breakage | Ease of troubleshooting |
|---|---|---|---|
| Small, regular updates | One or two versions per component | Lower | Easier – few changes to isolate |
| Occasional batch updates | Several versions across many plugins | Moderate | Harder – many simultaneous changes |
| Updating after years of neglect | Major versions of core, plugins and PHP | Higher | Difficult – often requires rebuild of parts of the site |
When a site has been neglected for long enough, the safest route forward sometimes involves replacing abandoned plugins, rebuilding parts of a custom theme or migrating to a new hosting environment, rather than simply clicking "update all".
Why updates sometimes break sites
It is worth being honest: updates do occasionally cause problems. Common reasons include:
- A plugin update changes behaviour that a custom theme or code snippet relied on.
- Two plugins load conflicting versions of the same JavaScript library.
- A page builder update changes how existing layouts render.
- Caching layers serve stale CSS or JavaScript after an update.
- An update runs out of memory or times out halfway through, leaving the site in maintenance mode.
Custom code and direct edits
Problems are more likely when a site has been modified in ways that updates do not expect. Edits made directly to a plugin's or parent theme's files are overwritten the moment that component updates, silently removing a fix or feature someone added years ago. Custom functionality should live in a child theme or a small site-specific plugin, and any changes should be held in version control so they can be reviewed and reapplied. If you inherit a site and are not sure whether this has happened, comparing installed plugin files against the official released versions will reveal any local modifications before they cause a surprise.
These risks are real, but the answer is to manage them, not to stop updating. A site that never updates is not avoiding risk; it is trading a small, controlled risk for a larger, uncontrolled one.
How to update WordPress safely
A sensible update process looks like this:
- Take a fresh backup of files and database, stored off the server, and confirm it completed. Our guide on how often a website should be backed up covers frequency and retention.
- Apply updates on a staging copy first, especially for core major releases, WooCommerce, page builders and anything touching checkout or forms.
- Test key journeys on staging: homepage, navigation, forms, search, login, basket and checkout.
- Update production in a planned window, ideally at a quieter time of day.
- Clear caches – plugin, server and CDN – and re-test the same journeys on the live site.
- Check error logs for new PHP warnings or fatal errors.
- Record what changed, including version numbers, so any later problem can be traced quickly.
You should also review the plugin list periodically: remove anything inactive, replace anything abandoned and consolidate plugins that duplicate functionality. Fewer, well-maintained plugins mean a smaller attack surface and fewer conflicts.
Should you rely on automatic updates?
WordPress can apply minor core releases automatically, and plugin and theme auto-updates can be enabled individually. Automatic updates are useful for low-risk components and security releases, but on business-critical sites – particularly stores – they can apply changes without anyone testing or watching. A common compromise is to allow automatic minor core security releases while handling plugins, themes and major releases through a tested, staged process with monitoring in place to catch failures.
Conclusion
Not updating WordPress does not usually break your site today. It makes your site steadily easier to compromise, more fragile when the hosting environment changes and more expensive to bring back up to date. Small, regular, tested updates backed by verified backups are the most reliable way to keep a WordPress site secure and working.
If keeping up with updates has become a burden, our WordPress maintenance service handles staging-first updates, backups, monitoring and reporting, and WordPress security adds hardening and continuous security monitoring. To find out how far behind your site currently is, start with a free website health check.