Update WordPress components

cPFence lets you update WordPress core, plugins, themes and translations without signing in to every site. Back up the sites and check public pages before beginning.

WebUI method

1. Select the intended sites.
2. Choose Bulk tools → Updates → Update WordPress components.
3. Choose All components, WordPress core, Plugins, Themes or Translations in Component.

Choose the Component and check the selected sites and servers before reviewing the update. Select the image to view it full size; use your browser’s Back command to return.

4. Review and confirm. Check each site’s result and resolve failures individually.
5. Verify versions, public pages and sign-in; clear relevant caches after successful updates.

Choose components without logging into every site

The WebUI updater can refresh all components or just the selected component on your checked sites.

Preserve customized sites

For old or customized installations, review compatibility and use an individual maintenance plan rather than a broad rollout. Update can replace component files; keep a usable backup and a way to restore it.

A manual update is separate from future auto-update policy. For failures, use WordPress update and backup troubleshooting.

Command-line method

Step 1: Check the sites list

Sign in as root to the server hosting the sites. Refresh the list when installations have changed:

cpfence --generate-wp-sites-list

Review /var/log/cpfenceav/wp-sites-list.txt before proceeding. Terminal bulk updates use that server’s listed installations; they do not inherit your checked WebUI rows. For a small selected rollout, use the WebUI method above.

Step 2: Update the intended components

For an interactive update of core, plugins, themes and translations, run:

cpfence --bulk-update-wordpress

Follow its prompts and read the results for each site. For an automated update without confirmation, specify the component explicitly:

Update now	Command
All components	cpfence --bulk-auto-update-all-sites all
WordPress core	cpfence --bulk-auto-update-all-sites core
Plugins	cpfence --bulk-auto-update-all-sites plugins
Themes	cpfence --bulk-auto-update-all-sites themes
Translations	cpfence --bulk-auto-update-all-sites translations

Automated updates start without confirmation

These commands update the server’s listed sites immediately. Review compatibility, backups and the intended list first. Read individual failures even when a completion message appears; resolve those sites before repeating a rollout.

The updater checks site loading and can remove a stuck .maintenance file. Still verify public pages and sign-in yourself; an automated response check cannot prove every page or plugin works.

Step 3: Review future updates and vulnerabilities

Use auto-update policy to enable or disable future updates for the intended components. For older or customized sites, use an individual maintenance plan instead of enabling broad automation.

Export a vulnerability report to help plan follow-up work:

cpfence --vuln-export

See download and analyze the CSV. The report identifies known vulnerabilities; it does not apply another update.