Allow safe database results or exclude a site

Use database exceptions for verified safe data that the WordPress database scan repeatedly reports. A result exception and a full-site exclusion have different scope.

Allow a safe result

1. Open Edit Configuration Files and select the server hosting the site.
2. Choose Database scan result allowlist.

Use narrow patterns for verified safe results; this list applies across the selected server. File contents are concealed for privacy. Select the image to view it full size; use your browser’s Back command to return.

3. Add a narrow regular expression matching the verified safe result, one entry per line. Plain text matches that text; escape regular-expression punctuation when you intend it literally.
4. Select Save changes and inspect validation errors.
5. Run Scan databases for malware for the affected selected sites and review the results.

Result patterns apply across the server

A broad pattern can hide unrelated findings. Check the reported database content before allowing it. Invalid expressions prevent the policy from loading.

Exclude an installation’s database

1. Choose Database scan site exclusions on the same server.

Choose the intended site-exclusion list and keep installation versus account-path scope clear. File contents are concealed for privacy. Select the image to view it full size; use your browser’s Back command to return.

2. Add the intended site’s full path, one entry per line. Use the installation path for one site; an account path can match several installations beneath it.
3. Save and inspect the next scan’s per-site output.

Keep module exceptions separate

These lists affect database scanning. They do not exclude filesystem malware findings or daily AutoShield policy. Remove the entry to resume the omitted check.