Vulnerability Monitor for Wordfence Intelligence

Changelog

1.3.10

  • Fixed a case where vulnerability notification emails could be sent but the scan summary in the WordPress admin page did not persist or display the latest results.

1.3.9

  • Stored scan result and operational status options with autoload disabled to reduce unnecessary front-end option loading.

1.3.8

  • Replaced inline admin CSS and JavaScript with properly enqueued assets.
  • Documented the Wordfence external service usage, data flow, and policy links in the readme.
  • Renamed generic runtime identifiers to stronger wfim-prefixed names to reduce conflict risk.

1.3.7

  • Renamed the public plugin package and release metadata for the new WordPress.org naming requirements.
  • Updated the public slug, text domain, and bundled archive structure to match the new plugin name.

1.3.6

  • Optimized feed matching so scans no longer re-scan the full installed plugin and theme lists for every feed item.
  • Reduced the risk of 30-second timeouts on larger Wordfence Intelligence v3 feeds.

1.3.5

  • Updated release metadata for the WordPress 7.0 compatibility check.
  • Bumped the packaged plugin version to 1.3.5.

1.3.4

  • Added an admin confirmation notice after sending a test email.
  • Improved test email feedback so successful sends are visible immediately in settings.

1.3.3

  • Fixed WordPress.org Plugin Check findings in the admin UI and packaging metadata.
  • Aligned plugin headers and readme requirements for WordPress.org submission.
  • Cleaned the release package and removed development-only warnings.

1.3.2

  • Distributed scheduled scans across sites using a stable per-site offset, reducing simultaneous Wordfence API requests.
  • Re-aligned existing scheduled scans to the new staggered timing after settings updates and plugin load.

1.3.1

  • Added detailed diagnostics for Wordfence feed fetch failures, including HTTP 429 rate-limit hints.
  • Preserved debug logs for failed scans so API error details remain visible in Scan Summary.

1.3.0

  • Added operational alert emails for scan failures, overdue scheduled scans, and fatal plugin errors.
  • Added recovery emails when scanning starts working again.
  • Added throttling to reduce repeat alert spam.

1.2.1

  • Improved the settings UX by moving the API key directly below the feed URL and removing the misleading “optional” label.

1.2.0

  • Migrated the default vulnerability feed from Wordfence V2 to V3.
  • Automatically upgrades the legacy V2 endpoint to the V3 endpoint in plugin settings.
  • Shows a clear admin error when the required Wordfence API key is missing.

1.1.0

  • Fixed send_only_new email logic so only genuinely new findings trigger notifications.
  • Added feed caching based on the configured cache TTL.
  • Made scheduled/manual scan failures return gracefully instead of terminating abruptly.
  • Fixed the deactivation modal stylesheet.

1.0

  • Initial public release.

Plugin Website
Visit website

Author
Interaktiv
Version:
1.3.10
Last Updated
June 25, 2026
Active Installs
10
Requires
WordPress 5.6
Tested Up To
WordPress 7.0
Requires PHP
7.2

Share Post

Join our newsletter.

Get insights into what’s happening at ChangelogWP right in your inbox. We don’t believe in spam.