All case studies

What does WordPress security and maintenance involve?

Security starts with knowing what your website runs, who updates it and how you recover when an update causes problems.

Read the key findings

TL;DR

  • Most reported issues in this dataset were in plugins. Of the 11,334 WordPress ecosystem vulnerabilities Patchstack reported for calendar 2025, 91% were in plugins. Check which plugins your own site needs and who maintains them.

    See what the 2025 records cover
  • Keep the whole stack in view. WordPress core, plugins, themes and the PHP runtime have separate update and support schedules. Check each one on the actual site.

    Check the PHP support schedule
  • Plan an update and recovery routine. A current backup, compatibility checks and a post-update review make it easier to keep the site working while updates are applied.

    See a practical upkeep routine
New WordPress ecosystem vulnerabilities reported by Patchstack for each calendar year
  • Calendar 20247,966
  • Calendar 202511,334

Patchstack recorded 42% more vulnerabilities in calendar 2025 than in calendar 2024. Both totals come from the same commercial disclosure coordinator.

See how it was measured

Risk is specific to the site you run

The work involved in keeping a WordPress site secure depends on the plugins, theme, hosting and versions it uses. Assigning an update owner and testing recovery are practical steps you can take for any setup.

Patchstack’s reports describe the ecosystem. Use the update and support guidance alongside them to check your individual installation.

Aggregate vulnerability reporting

The 2025 records rose, with plugins accounting for most disclosures

Patchstack reported 11,334 newly disclosed vulnerabilities across the WordPress ecosystem for calendar 2025, 42% more than its 7,966 records for calendar 2024. In the 2025 set, 91% were in plugins, 9% in themes, and six low-priority issues in core.

New WordPress ecosystem vulnerabilities reported by Patchstack for each calendar year
  • Calendar 20247,966
  • Calendar 202511,334

Patchstack is a commercial vulnerability intelligence provider and disclosure coordinator. Changes in what researchers discover and report can affect the annual totals. The dataset counts vulnerability records across components.

Start by listing the plugins and theme on your own site. Check which you still use, which are supported and who receives update notices.

Patchstack, State of WordPress Security in 2025 and State of WordPress Security in 2026, covering calendar 2024 and 2025. Read Patchstack’s 2026 report

WordPress project maintenance guidance

Updates need a recovery plan and a check that the site still works

Take a current backup, apply updates and test that customers can still enquire or book.

WordPress documents automatic background updates for certain releases and individual controls for plugin updates. The team looking after your site can check which updates run automatically and who reviews problems.

After an update, try submitting an enquiry and confirm it reaches the right inbox. If you take bookings online, check the calendar and the customer confirmation. Check periodically that a backup can be restored.

WordPress.org, Updating WordPress (accessed 21 November 2026). Read WordPress update guidance

Runtime lifecycle policy

Check the PHP version separately from WordPress components

The PHP project gives release branches two years of active support followed by two years of critical-security-only support, then end of life. At the 21 November 2026 snapshot, PHP 8.2 security support was scheduled through 31 December 2026.

Runtime support follows a separate schedule. Ask your host or developer which PHP branch the site runs and when they plan to upgrade it.

Plan a compatibility check after a runtime change. Include form delivery, booking calendars and payment steps where those features are part of the site.

PHP project, Supported Versions (accessed 21 November 2026). Check PHP’s supported versions

Start with an inventory and a recovery check.

The useful question is whether your site’s components are supported and whether someone can restore the customer journey if a change causes a problem. Make the routine visible before deciding whether to keep managing it in-house or ask for help.

  1. List the WordPress core, theme, plugins and PHP versions in use, along with update dates and the person responsible for each.
  2. Confirm that backups are current and restorable. After an update, test the pages and actions that bring enquiries, bookings or sales.
  3. Remove components the site no longer needs and review unsupported items with the developer or host before changing production.

Start by checking the records for your own site and assigning someone to fix the clearest gap.

Explore website design and development