diff --git a/Screenshot_495.png b/Screenshot_495.png
deleted file mode 100644
index 346683a..0000000
Binary files a/Screenshot_495.png and /dev/null differ
diff --git a/Screenshot_496.png b/Screenshot_496.png
deleted file mode 100644
index 43add5a..0000000
Binary files a/Screenshot_496.png and /dev/null differ
diff --git a/changelog.txt b/changelog.txt
index d2701a0..6167a92 100644
--- a/changelog.txt
+++ b/changelog.txt
@@ -1,5 +1,12 @@
 == Changelog ==
 
+= [5.0.1] - 2026-06-02 =
+
+**Fixed**
+
+* `wp_cache_flush()` removed from `wpvulnerability_update_database_data()` and `wpvulnerability_reset_plugin_data()`. The function was wiping the entire Object Cache (Redis, Memcached, APCu) on every plugin or theme update, causing CPU spikes and database overload on high-traffic sites. The targeted `wpvulnerability_delete_transients()` call that already runs before it invalidates all plugin-owned cache entries; a global flush was never necessary.
+* `wp_cache_flush()` was called twice on plugin reset: once inside `wpvulnerability_update_database_data()` and once more immediately after in `wpvulnerability_reset_plugin_data()`. Both calls have been removed.
+
 = [5.0.0] - 2026-05-26 =
 
 **Added**
diff --git a/languages/messages.mo b/languages/messages.mo
deleted file mode 100644
index 543b83c..0000000
Binary files a/languages/messages.mo and /dev/null differ
diff --git a/readme.txt b/readme.txt
index a1f3865..f315a69 100644
--- a/readme.txt
+++ b/readme.txt
@@ -3,9 +3,9 @@ Contributors: javiercasares, davidperez, lbonomo, alexclassroom
 Tags: security, vulnerability, site-health
 Requires at least: 5.6
 Tested up to: 7.1
-Stable tag: 5.0.0
+Stable tag: 5.0.1
 Requires PHP: 7.0
-Version: 5.0.0
+Version: 5.0.1
 License: GPL-3.0-or-later
 License URI: https://spdx.org/licenses/GPL-3.0-or-later.html
 
@@ -201,6 +201,12 @@ First of all, peace of mind. Investigate what the vulnerability is and, above al
 
 == Changelog ==
 
+= [5.0.1] - 2026-06-02 =
+
+**Fixed**
+
+* `wp_cache_flush()` removed from the plugin/theme update hook and the plugin reset routine. The function was wiping the entire Object Cache (Redis, Memcached, APCu) on every update, causing CPU spikes on high-traffic sites. The targeted transient cleanup that already runs before it is sufficient.
+
 = [5.0.0] - 2026-05-26 =
 
 **Added**
diff --git a/wpvulnerability-run.php b/wpvulnerability-run.php
index d0a061d..707d30d 100644
--- a/wpvulnerability-run.php
+++ b/wpvulnerability-run.php
@@ -78,9 +78,6 @@ function wpvulnerability_update_database_data() {
 	}
 
 	wpvulnerability_statistics_get();
-
-	// Clean the WordPress cache.
-	wp_cache_flush();
 }
 
 /**
@@ -531,7 +528,6 @@ function wpvulnerability_reset_plugin_data() {
 	}
 
 	wpvulnerability_update_database_data();
-	wp_cache_flush();
 }
 
 /**
diff --git a/wpvulnerability.php b/wpvulnerability.php
index fcf2492..18d9916 100644
--- a/wpvulnerability.php
+++ b/wpvulnerability.php
@@ -5,7 +5,7 @@
  * Description: Receive information about possible vulnerabilities in your WordPress from WordPress Vulnerability Database API.
  * Requires at least: 5.6
  * Requires PHP: 7.0
- * Version: 5.0.0
+ * Version: 5.0.1
  * Author: ROBOTSTXT
  * Author URI: https://www.robotstxt.es/
  * License: GPL-3.0-or-later
@@ -15,7 +15,7 @@
  *
  * @package WPVulnerability
  *
- * @version 5.0.0
+ * @version 5.0.1
  */
 
 defined( 'ABSPATH' ) || die( 'No script kiddies please!' );
@@ -23,7 +23,7 @@ defined( 'ABSPATH' ) || die( 'No script kiddies please!' );
 /**
  * Set some constants that I can change in future versions.
  */
-define( 'WPVULNERABILITY_PLUGIN_VERSION', '5.0.0' );
+define( 'WPVULNERABILITY_PLUGIN_VERSION', '5.0.1' );
 define( 'WPVULNERABILITY_API_HOST', 'https://www.wpvulnerability.net/' );
 
 /**