WordPress maintenance is the recurring work of keeping core, plugins, themes, and the server platform updated, backed up, and secure — plus the review work of deciding which components still deserve a place on the site. It is not a single task but a cycle: update, verify, back up, test, and periodically audit what is installed.
Most of that work is driven by third-party code rather than WordPress itself. Patchstack's *State of WordPress Security in 2026* counted 11,334 new vulnerabilities across the WordPress ecosystem in 2025, a 42% year-over-year rise, with 91% of them in plugins, 9% in themes, and six in core. A maintenance plan that only tracks WordPress version numbers is watching the smallest part of the surface.
Table of Contents
- Core updates, and why "patched" needs verifying
- Why updating alone cannot close every hole
- Auditing the plugin and theme inventory
- Backups you have actually restored
- The platform underneath moves too
- Frequently Asked Questions
Core updates, and why "patched" needs verifying
WordPress 6.9.2, released on 10 March 2026, fixed ten security issues, and the release notes urged site owners to update immediately. A follow-up 6.9.4 was then required because three of those ten fixes had not been merged into the 6.9 branch — a reminder that applying an update is not the same as confirming the fix landed on your install. Only the most recent release line receives active support, according to WordPress's own version documentation.
A site parked on an older branch does not quietly receive backported fixes; it accumulates unpatched flaws while still reporting a version number that looks deliberate. Automation covers part of this and no more. `WP_AUTO_UPDATE_CORE` defaults to `minor` on stable installs and accepts `false`, `minor`, or `true` (dev, minor, and major), and defining the constant overrides the admin auto-update interface. Plugin updates, theme updates, and major-version jumps stay a deliberate human decision — which is exactly where the scheduled maintenance window earns its keep.
Why updating alone cannot close every hole
Patchstack's 2026 report found 46% of disclosed vulnerabilities had no patch available at the point of disclosure. For nearly half of what gets published, there is nothing to click: the only remedies are removing the component, replacing it, or shielding it at the firewall until a fix appears. That changes the shape of the job.
A maintenance routine built entirely around "run the updates" has no answer for an unpatched plugin, so the inventory review — what is installed, what it does, whether anything still depends on it — becomes the part that actually resolves those cases. Delegating the problem upward does not work either. Patchstack's 2025 penetration testing found typical hosting defenses blocked only 26% of exploit attempts and just 12% of WordPress-specific attacks. "The host handles security" describes a layer that misses most of what targets WordPress specifically.
Auditing the plugin and theme inventory
Wordfence defines an abandoned plugin as one its developers have not updated for at least two years, and recommends removing immediately any plugin pulled from the repository over an unfixed vulnerability. Both conditions are invisible from the WordPress dashboard, which shows available updates but not the absence of a maintainer.
A practical quarterly pass: The outcome of an audit is often subtraction. Every plugin you remove is a dependency you no longer have to monitor, patch, or test against the next core release.
- List every active plugin and theme, with its last-updated date.
- Flag anything untouched for two years or more as a replacement candidate.
- Check whether each flagged plugin is still listed in the WordPress.org repository; a removed listing is a signal to act, not to wait.
- Delete deactivated plugins rather than leaving them installed — inactive files still sit on disk.
- Record which plugin provides each business-critical feature, so a removal decision is not blocked by uncertainty.
Backups you have actually restored
WordPress's backup documentation states that a restorable backup needs two parts: the database — posts, pages, comments, settings — and the files, meaning core, plugins, themes, uploads, `wp-config.php`, and the whole `wp-content` directory. A database dump without the uploads directory restores a site with no images. The same documentation advises backing up before every upgrade.
That pairing is the point: the backup is what makes a routine update a reversible action instead of a gamble on a live site. Run the update on a staging copy first where one exists, then on production with a fresh backup in hand. Test the restore, not just the backup job. A backup that has never been restored is an untested assumption, and the moment you discover a missing table or an excluded directory should not be the moment the site is down.
The platform underneath moves too
PHP and MySQL versions are recurring maintenance, not setup you finish once. WordPress's requirements page sets PHP 8.3 or greater plus MySQL 8.0 or MariaDB 10.11 or greater as the baseline, while the Hosting Handbook for WordPress 7.1 recommends PHP 8.4 or newer for production and notes that MySQL 8.0 reached end of life on 30 April 2026.
The PHP release calendar sets the pace. Each branch receives two years of active support followed by two years of security-only fixes; as of 20 November 2026, php.net's supported-versions page puts the end of PHP 8.2's security support at 31 December 2026 and PHP 8.3's at 31 December 2027, and warns that users of end-of-life versions "may be exposed to unpatched security vulnerabilities." Those dates are the useful part of the plan, because they are known in advance. A site on PHP 8.2 today has a deadline in roughly six weeks; a site on 8.3 has a year to schedule compatibility testing for its theme and remaining plugins, which is exactly the kind of work that goes badly when it is done in a hurry.
Frequently Asked Questions
How often should maintenance run?
Security releases are handled as they appear — WordPress 6.9.2's notes urged owners to update immediately. Plugin and theme inventory reviews work better on a fixed quarterly schedule, and platform upgrades are planned against the published PHP end-of-life dates.
Is auto-update enough for plugins?
No. `WP_AUTO_UPDATE_CORE` governs core only, and 46% of vulnerabilities Patchstack recorded had no patch at disclosure, so some components need replacing rather than updating.
What belongs in a backup besides the database?
WordPress's documentation lists core files, plugins, themes, uploads, `wp-config.php`, and the entire `wp-content` directory alongside the database.




