Back to Community
Home / Community / General

Why Sucuri Security Shows 'Untested with Your WordPress Version' and What to Do

38 threads Sep 17, 2025

Content

If you use the Sucuri Security plugin, you've likely seen the warning message: "This plugin has not been tested with your current version of WordPress." This is a common point of confusion and concern for users who rely on the plugin for their site's security. This article explains why this message appears and what it means for the safety and functionality of your website.

Why Does This Message Appear?

This warning is generated by the WordPress.org plugin repository, not by the Sucuri Security plugin itself. For a plugin to display as "tested" with a specific WordPress version, its author must update a specific version number in its `readme.txt` file on WordPress.org. The message does not automatically mean the plugin is broken or incompatible.

Based on historical responses from the Sucuri Security development team, this often happens because:

  • The team is working on a significant internal update, reducing the time available to immediately update the public `readme.txt` file.
  • The plugin undergoes a quality assurance (QA) process before new versions are released, which can delay the update of the "tested up to" version in the repository.
  • The developers actively test the plugin against development versions of WordPress, meaning it's often compatible with new releases before the public version number is officially updated.

Is the Plugin Still Safe to Use?

In nearly all cases, yes. The Sucuri Security team has repeatedly confirmed that the plugin's code is designed to be compatible with a wide range of WordPress versions. The plugin uses core PHP functions and WordPress APIs in a way that is not typically broken by routine WordPress updates.

As stated in the support forums: "The code is not dependent on any breaking changes inserted by the WordPress core developers in the newer releases. Unless WordPress introduces really big breaking changes the plugin will keep working." Many Sucuri employees and a vast user base run the plugin on the latest WordPress versions without issues.

What You Can Do

  1. Update with Confidence: You can usually install or update the plugin despite the warning. The consensus from numerous support threads is that the plugin remains functional and secure.
  2. Test on a Staging Site: If you are managing a critical business website, the best practice is always to test any updates, including plugins, on a staging or development site first. This allows you to confirm compatibility without affecting your live site.
  3. Wait for the Repository Update: If the message causes concern, you can wait. The Sucuri Security team consistently updates the "tested up to" value in the repository after their internal QA process is complete for a new release. This typically happens within a few weeks of a major WordPress update.

When to Be Concerned

The "untested" warning is generally a false positive. However, if you actually encounter a bug, error, or strange behavior after a WordPress update, the issue should be investigated. In such cases, you can seek help from the wider community or report the specific problem on the plugin's support forum for assistance.

In summary, the "untested" warning is almost always a administrative delay, not a reflection of the plugin's actual compatibility. You can continue to use Sucuri Security to help protect your website.

Related Support Threads Support