How to Back Up and Verify WordPress 7.1.3 in cPanel

Before updating WordPress, check the installed version and confirm you have a recent backup of both the site files and its database, plus a workable way to restore them. Then update through the dashboard if that option is available, and verify the version, a public page, and the site’s main workflow. cPanel backup and restore options vary by host, so a backup file by itself is not proof that recovery is possible.

This guide is for WordPress site operators using cPanel. WordPress announced 7.1.3 on October 6, 2026, as a security and maintenance release with seven security fixes and four bug fixes, and recommends updating. That does not mean every site is affected by every issue addressed in the release. WordPress News: 7.1.3 Maintenance and Security Release

Check whether the site still needs the update

Sign in to the WordPress administration area and check the version shown in the administration footer. WordPress documents this as one place to find the installed version; screen details can vary by version or configuration. WordPress Documentation: Administration Screens
Open Dashboard > Updates and review the version and update information shown there. Check even if you suspect the site updated automatically: the 7.1.3 announcement says eligible sites may receive the release in the background, but eligibility varies.
If the site already reports 7.1.3 or a later applicable release, record that and do not reapply 7.1.3. If it reports an earlier version, continue with the backup checks before updating.

Confirm the backup covers files and database

A typical WordPress recovery needs both the site files and its database. A copy of the WordPress directory alone does not normally include the separate database. WordPress Developer Resources: Backups

In cPanel, look for the Backup interface, commonly listed under Files. If you cannot find it, or its options differ from the instructions you have, ask your hosting provider what backup features are enabled for your account. The provider can enable or disable cPanel’s Backup interface. cPanel & WHM Docs: Backup for cPanel
Identify what the available backup contains. Confirm that it covers the files for this WordPress installation and the database used by this site. Check the backup date and confirm it is recent enough for your recovery needs and was created before the update. If the interface does not make the contents clear, ask the host where the database backup is stored and how to identify it.
Confirm where the backup is stored and how you would restore it. Ask whether it would remain accessible if the hosting account or server had a problem, and who performs the restoration. Do not assume a file is complete or recoverable just because it appears in cPanel.

cPanel distinguishes partial backups from full account backups. Partial backup files store individual account parts and can be restored through cPanel when that functionality is available. A full account backup cannot be automatically restored through cPanel; cPanel says WHM or the hosting provider is needed for automatic full-backup restoration. Your host’s configuration determines which options are available, so confirm the restore route for your account rather than relying on the backup label alone.

Hypothetical example: full backup download, no restore control

Suppose your cPanel account offers a full-backup download but shows no restore control. Before updating, ask your host: Can you restore this full account backup through WHM or another supported process? Where is the database backup for this WordPress site, and how would it be restored? If you cannot establish that the backup includes the site’s files and database and that a usable restore route exists, resolve that with the host before treating the backup as your recovery plan.

Update through WordPress

WordPress’s general update guidance recommends making a backup before updating. When the dashboard offers the release, go to Dashboard > Updates and select Update Now. The 7.1.3 release notice lists that route as an update option. WordPress Documentation: Updating WordPress

If the one-click update fails or is unavailable, filesystem permissions can be one reason WordPress cannot complete it. Do not change server permissions based on guesswork. Ask your hosting provider or site administrator to confirm the appropriate update method for this installation.

Verify the update and the site’s important workflow

An update confirmation is not a recovery test, and it does not show that every public page or business workflow works. After updating:

Check the administration footer or Dashboard > Updates again. Confirm the site reports 7.1.3 or a later applicable release.
Open an important public page in a browser and check that it loads and displays as expected.
Test the workflow that matters for this site. For a lead-generation site, submit a form using an appropriate test procedure and check whether the expected confirmation appears. For a WooCommerce store, follow the store’s safe checkout test procedure. A brochure site without a form or checkout may need a different functional check.
Record any error messages or unexpected behavior, including where they appeared and what action triggered them. If a workflow fails, contact the site administrator or host with those details; do not assume the update notice identifies the cause.

Quick verification checklist

Before updating: record the installed version and confirm a recent, pre-update backup covers both files and the relevant database.
Before updating: confirm the backup’s location and a usable restore route with the host.
After updating: confirm the reported version, load a public page, and test the site’s actual key workflow. Record any errors.

Which part of your cPanel recovery plan was hardest to verify: the database backup, the backup’s location, or the restore process? Share your experience without posting account details or other sensitive information.

Sources

Editorial note: AI assists with research, drafting and automated checks. Sources are linked so you can verify the guidance. Platform requirements can change; confirm the details that apply to your setup.