Integrity scanner aborts scanning on sites with a digit-leading database table prefix

Status: Confirmed
Affected version: WP Cerber 9.7.4
Affected setup: WordPress sites where the database table prefix starts with a digit, for example $table_prefix = '1_';
Fix status: A maintenance update is planned for this week.

In WP Cerber 9.7.4, we added stricter validation for internal database operations. This was intended to make database handling safer, but it introduced a regression for one valid WordPress edge case: database table prefixes that start with a digit.

On affected sites, the integrity scanner aborts the scanning process shortly after it starts. Sites using prefixes without a leading digit such as wp_ are not affected by this issue.

Symptoms

When you click Start Quick Scan or Start Full Scan , the scanner starts and then immediately stops with the message: “The scan has finished.”

The same issue affects scheduled scans.

Workaround

At this point, we recommend waiting for the upcoming maintenance update. Enable automatic updates for WP Cerber to have the update installed automatically as soon as it becomes available.

Fixed in WP Cerber 9.8.