WP Cerber 9.9 is out

This release focuses on two areas that matter when something goes wrong: preserving a valid plugin configuration and detecting more forms of obfuscated JavaScript in incoming requests. It also improves compatibility with hosting environments that do not provide the mysqlnd database driver.

Automatic backup and recovery for plugin settings

WP Cerber now keeps a last-known-valid backup of its settings.

The backup is refreshed after successful settings updates, imports, plugin upgrades, and daily maintenance. An invalid configuration cannot replace the existing valid backup.

If the settings stored in the WordPress database become corrupted or unreadable, WP Cerber attempts to restore the last valid configuration automatically. This helps preserve firewall rules, notifications, and other plugin settings instead of immediately falling back to defaults.

The recovery process is reported through the issue monitor:

  • A successful recovery produces a dismissible warning that explains what happened and what should be reviewed.
  • A failed recovery produces a critical issue with diagnostic information and practical guidance.
  • Duplicate or contradictory recovery notices are prevented.

This also fixes a PHP 8 scenario where corrupted settings could trigger a fatal TypeError during plugin initialization and take the website down.

Traffic Inspector detects more obfuscated JavaScript

We made several changes to the Traffic Inspector detector that screens public request fields for obfuscated JavaScript.

The detector now handles more escape formats, including Unicode escapes, and inspects code reconstructed from String.fromCharCode() calls more thoroughly. It also recognizes payloads that use wrapped integer values, unsupported tokens, or JavaScript comments to interfere with decoding.

These changes close several practical bypasses while keeping the detector deliberately conservative. Partial expressions and ambiguous input remain outside the detection scope where supporting them would create an unreasonable false-positive risk.

The release also fixes a regression that prevented some strings composed entirely of \xNN hex escapes from being decoded correctly.

Better compatibility with hosts without mysqlnd

Some hosting environments provide the PHP mysqli extension without the mysqlnd driver. On those systems, database operations that relied on fetch_all() could cause a fatal error.

WP Cerber now detects whether that method is available. When it is not, the plugin uses a compatible row-by-row fallback instead.

The plugin remains functional, although the fallback may be slower. A new advisory in the System Readiness widget explains the condition and recommends enabling mysqlnd for full compatibility and better performance.

1 Like

Hello WP Cerber Team,

I would like to report what appears to be a regression (or at least a false positive) introduced after updating to WP Cerber 9.9.

Environment

  • WordPress: Latest available version

  • WooCommerce: Latest available version

  • WP Cerber: 9.9

  • ActiveLayer: Installed

  • Multilingual website

  • Customer registration enabled on the WooCommerce “My Account” page

WooCommerce Account Settings

The following options are enabled:

  • Allow customers to create an account on the “My Account” page

  • Allow customers to create an account during checkout

  • Allow login during checkout

  • Send password setup link

  • Generate username automatically

Guest checkout is disabled.

These settings had been working correctly before the issue appeared.

Timeline

  • Last successful customer registration: July 14, 2026 at 12:26 PM

  • Last order placed by a newly registered customer: July 14, 2026

  • First customer report of the issue: July 15, 2026

  • WP Cerber was updated to version 9.9 on July 14, 2026.

The timing strongly suggests that the issue started immediately after updating to version 9.9.

Problem Description

New customers are no longer able to register from the WooCommerce “My Account” page.

The issue affects only new user registration.

Existing users can log in normally without any problems.

When attempting to register:

  • WooCommerce displays the error:

    “Not enough data to create this user.”

  • ActiveLayer may classify the request either as “Clean” or occasionally as “Spam”, but disabling ActiveLayer does not resolve the problem.

  • WP Cerber logs the event as:

    “Registration attempt denied – Bot detected.”

  • No WordPress user account is created.

Troubleshooting Performed

The following tests were performed without resolving the issue:

  • Disabled ActiveLayer completely.

  • Disabled WooCommerce options:

    • Send password setup link

    • Generate username automatically

  • Tested registration in different website languages.

  • Repeated the tests using new email addresses.

None of these actions solved the problem.

Important Finding

The only configuration change that immediately restored customer registration was disabling the following option:

WP Cerber → Anti-spam → Protect registration form with bot detection engine

After disabling only this option:

  • Customer registration works again.

  • ActiveLayer can remain enabled.

  • Existing user login continues to work normally.

  • New WordPress users are created successfully.

  • No IP whitelist is required anymore.

No other WP Cerber protection features were disabled.

Conclusion

Based on all tests, the problem appears to originate specifically from the Bot Detection Engine protecting the WooCommerce registration form.

It seems that legitimate WooCommerce registration requests are being incorrectly classified as bots, preventing user creation.

Because the issue started immediately after upgrading to version 9.9, there may be a regression or a change in the bot detection heuristics that affects some WooCommerce installations.

Request

Could you please investigate whether this behavior is related to changes introduced in WP Cerber 9.9?

If necessary, I would be happy to provide:

  • additional debug logs;

  • Activity Log entries;

  • Traffic Inspector logs;

  • screenshots;

  • information about my hosting environment;

  • plugin list;

  • steps to reproduce the issue.

Thank you for your excellent work on WP Cerber and for looking into this issue.

Kind regards,
Ivan