Check WordPress integrity and review results

In cPFence v4+, Threat & Malware Detection → WordPress Integrity lists sites and their recorded core-file checks. Support users need access to the target servers and permission to view history and findings; starting a check also needs scan permission.

Find the sites

1. Open WordPress Integrity and choose Local, one secondary server, All Servers or All Servers (No Local). Use Select servers to choose a server subset before filtering or selecting sites.
2. Search sites, domains or paths, choose Owner and Status, then Apply filters. Use Clear to reset the filters.
3. Review Sites, Checked, Findings and Quarantined. Use Previous and Next to read additional sites or recent checks.
4. Open a site’s Details or an entry under Recent integrity checks.

Select a summary card to narrow the results; select it again to clear that card’s filter.

Filter the inventory before selecting sites. Identifying values are concealed; displayed checks are retained records. Select the image for full size; use browser Back to return.

Status choices distinguish Clean, Issues found, Not checked, Failed or incomplete, Excluded or skipped and Quarantined. An excluded or unchecked site is not a clean result.

Read a check’s details

Check Status, Site, Server, Owner, Started, Duration, Findings, Quarantined and Core repair. Read the Findings and Recorded actions separately; expand Earlier checks for this site to compare retained records. Copy site ID can help identify the intended site when contacting support; keep identifiers private.

Excluded findings are not actionable. The details describe the recorded check, not a fresh inspection of every current file.

A retained Clean core check with no recorded core repair. Identifying values are concealed; this does not verify the whole site's current state. Select the image for full size; use browser Back to return.

Repair is not a clean result

If a record reports a completed core repair, run a subsequent complete integrity check to confirm clean core files. A clean core checksum does not establish that plugins, themes or accounts are clean.

Run an integrity check

Starting a check needs a connected target with an eligible license. See the shared scan prerequisites and server scope.

Automatic actions can change files

When enabled on a target server, automatic file actions may repair WordPress core files or quarantine unexpected files. Review the policy and backups before confirming. A submitted request or Finished output is not proof that every site completed cleanly.

1. Review integrity policy and exclusions. Preserve backups before allowing automatic file actions.
2. Filter the inventory, then select the intended sites. Select all visible covers the visible rows; Select all … filtered sites includes matches on other pages. Use Clear selection before choosing a different set.
3. Select Run integrity check to open Confirm integrity check.
4. Review Selected sites, Action and options, Target servers and each server’s Automatic file actions setting. If a setting is unavailable or the selection changed, refresh the inventory and review the targets again.

Review the sites and each target server's file-action policy before confirming. Identifying values are concealed; this review was cancelled without running a check. Select the image for full size; use browser Back to return.

5. Choose Cancel to leave without starting, or Run integrity check to submit the reviewed check.
6. Read every target’s output. After the request finishes, return and refresh the inventory or recent checks to inspect the recorded final result.

Use Copy output for a private record, Cancel to request cancellation, then Back and Refresh to check retained history; cancellation alone does not establish the final check status. If output shows Needs attention, a busy target or an interruption, inspect that history before retrying. For recovery, see restore quarantined files or restore WordPress core.