Description
Interaktiv Security Scanner checks installed plugins and themes for known vulnerabilities and monitors unexpected file integrity changes. Vulnerability Intelligence uses the Wordfence Intelligence v3 feed (object-map, array, and NDJSON formats; gzip-aware streaming) as its data source. The plugin is not affiliated with Wordfence.
This plugin is designed to be:
- Lightweight – uses the Wordfence feed API and official WordPress core and plugin checksum services.
- Privacy-friendly – no tracking or telemetry; vulnerability matching happens locally on your site.
- Memory-safe – supports streaming large NDJSON and gzip feeds without exhausting server memory.
- Fully configurable – email notifications, severity levels, scheduled scans, and more.
Perfect for agencies, freelancers, and site owners who want proactive security visibility without complexity.
Key Features
- Scan installed plugins and themes for known vulnerabilities.
- Supports NDJSON, array JSON, and object-map JSON feed formats.
- Handles gzip-compressed feeds automatically.
- Match detection for:
- severity levels (critical, high, medium, low)
- patched versions
- remediation steps
- Customizable email notifications with templates.
- Optional scheduled scans (hourly, daily, or custom).
- “Only notify on new issues” mode.
- Supports the current Wordfence Intelligence V3 API with API key authentication.
- Debug mode with detailed logs.
- No tracking or telemetry.
- Matching and reporting logic runs locally on your site.
- File integrity checks for WordPress core checksums, unexpected server-side files in uploads, .htaccess and critical files, plus selected custom components.
File Integrity
Interaktiv Security Scanner 1.5.0 compares affected plugins with WordPress.org checksums in bounded background jobs. A confirmed file mismatch is VERIFICATION_FAILED. VERIFIED_OFFICIAL means all manifest-listed files match and no unexpected files were observed during a completed check. Manifest completeness is not independently established. Unavailable checksums and interrupted checks are UNVERIFIED with distinct details. These results describe current files; they do not establish update origin, time, or freedom from malicious code. FIM findings remain visible and baseline acceptance is manual.
Plugin verification uses the directory name as the WordPress.org slug and the installed plugin version. It strictly checks manifest files, including readmes, and reports extra files. Legitimate local additions or readme differences can therefore produce a failure; investigate before deciding whether a file is malicious. Custom, premium, unsupported, or unavailable versions may have no official manifest and remain unverified. Verification has file, response-size and time limits and does not create an atomic filesystem snapshot. It cannot rule out concurrent changes after a file was checked. A manifest that omits both an official file and its missing local copy cannot be identified as incomplete without an independent reference.
Interaktiv Security Scanner 1.4.0 adds local change detection. It is not a malware signature scanner and does not remove, quarantine, or repair files. WordPress core files are compared with official checksums for the installed version and locale. If that service is unavailable, the result says verification was unavailable; files are not labeled compromised. Executable extensions in uploads include PHP, PHP3/4/5/7/8, PHTML and PHAR, case-insensitively.
Unexpected executable files in uploads are reported by relative path. For untrusted uploads, notification change detection uses the observed file modification time rather than a content hash; a content change that keeps the same path and modification time will not generate a new uploads-only notification. Detection does not imply that a file is malicious.
An index.php under wp-content/uploads/ is omitted from unexpected executable findings when it is zero bytes or its complete content is exactly <?php after optional leading UTF-8 BOM and surrounding whitespace. Files with comments or additional code remain findings. The check reads at most 65 bytes from candidates no larger than 64 bytes and saves no trust state.
Administrators can review unexpected executable uploads and explicitly trust individual file hashes. A changed trusted file is reported, and a missing trusted file is reported as deleted. Existing path-only allowlist entries do not confer trust. Trust records do not establish that a file is safe.
The admin page has separate Vulnerability Intelligence and File Integrity tabs. Vulnerability scanning remains the default; FIM is disabled on upgrade from 1.3.11 until explicitly enabled on its tab. Each module has its own manual scan, status and scheduled hook. Disabling FIM retains its baseline and results but stops new FIM scans and emails. The administrator saves plugin/theme selections in FIM settings, separately from explicitly creating or accepting a SHA-256 trusted baseline. Newly selected components remain pending until baseline acceptance; unselected components stop being compared without false deletion findings. A baseline trusts the current state; it does not prove the site is clean. No baseline is created during upgrade. Core checksum and uploads executable checks can run after FIM is enabled and before baseline initialization. .htaccess files are traversed, but .htaccess change findings require a trusted baseline. Normal scans never update or recreate the baseline. Rebuilding requires an administrator, nonce and confirmation checkbox, and is refused during an active scan. A failed or incomplete traversal cannot replace the existing baseline. A separate confirmed Reset FIM baseline action removes the trusted baseline, all baseline storage parts and previous FIM scan results without changing plugin settings, vulnerability results or schedules; a new baseline must be created explicitly.
The File Integrity tab starts with scan scheduling, followed by an overview, scan action, grouped findings and trusted uploads. Monitoring scope, trusted baseline controls, notifications and templates appear in separate sections. Component selection is searchable and shows unsaved changes. Save all FIM settings saves the monitoring scope and the other FIM settings together; baseline acceptance and reset remain separate confirmed actions using the saved scope. The baseline is a record of an explicitly trusted state, not proof that files are clean.
Both tabs edit the same notification email address. FIM has its own notification switch, finding categories, only-new-or-changed option, subject template ({site}, {count}, {time}) and plain-text body template ({site}, {count}, {time}, {status}, {affected}, {context}, {counts}, {list}, {warnings}). The default body summarizes scan completeness, affected files, findings, selected category counts, up to 20 relative paths and up to 10 warnings; it omits the Warnings section when there are none and never includes file contents. In a custom body template, an empty {warnings} becomes an empty string; any heading written by the administrator remains. Manual and scheduled FIM scans share one notification history: a new or changed finding sends one aggregate email, unchanged unresolved findings do not resend by default, and a clean scan resolves the incident so a later recurrence can notify again. A failed delivery remains eligible for retry on the next scan. A separate FIM test-email button renders the saved templates, marks the message as a test and does not change scan or notification history. The admin page checks saved state by AJAX and updates FIM results while scheduled plugin verification is active. Polling is bounded; if WP-Cron does not run or polling stops before verification finishes, refresh the page to check the saved results.
The plugin scans the WordPress root without following symlinks. Core and uploads directories are fully traversed, including .git and node_modules. Elsewhere, .git and node_modules directories are skipped with an explicit incomplete-scan warning, so a baseline cannot be accepted without inspecting those paths. Cache, backup and temporary directories are traversed. Cache, backup and temporary files are excluded from selected-component hashing. In selected components, log, archive, SQL and temporary file extensions are also excluded. The traversal enumerates all directories for .htaccess, symlinks and read errors, and caps selected-component entries and monitored critical files at 100,000 and traversal at 120 seconds. Ordinary uploads remain fully inspected for executable files within the time limit and the 20,000 executable finding cap. The trusted map is capped at 20,000 tracked files, 256 MiB per tracked file and 8 MiB of path/hash data. At most 200 example findings are stored for the UI. On an unreadable path, a limit, or a timeout, the scan is marked incomplete and baseline DELETED findings are suppressed. Custom uploads directories outside the WordPress root are reported as uninspected. Paths in results are relative; file contents are never stored.
FIM notifications use a separate state from vulnerability notifications. On a complete scan, an aggregate email is sent when the incident fingerprint (type, change, relative path and observed hash or uploads mtime) changes. On an incomplete scan, the plugin emails the first incomplete transition or eligible finding/warning change detected within the scanned area; unvisited files cannot be verified. An unchanged unresolved incident does not resend on every scan. A clean completed scan clears the incident state so a recurrence notifies again. Manual and scheduled FIM scans both use this policy. FIM and vulnerability scans run independently. On feed failure, the previous successful vulnerability result remains visible with a stale warning and its last successful timestamp.
How It Works
The plugin fetches the Wordfence Intelligence feed, streams it in a memory-safe way, and compares each entry with your installed plugins/themes.
You can trigger scans:
- manually from the WP Admin panel
- or automatically via the scheduled scan option
The results include severity, details, patched versions, and links to advisories.
External services
This plugin connects to the Wordfence Intelligence vulnerability feed provided by Defiant, Inc. to download vulnerability data used for scans.
When file integrity monitoring is enabled, it requests official core checksums from api.wordpress.org for the installed WordPress version and locale, plus en_US for localized installations. If the English request fails, ambiguous mismatches remain unverified. The request does not upload local file contents or the baseline. It sends the version, locale and normal HTTP connection metadata. If the checksum API cannot be reached, core verification is marked unavailable; local uploads and baseline checks continue.
For affected plugins, FIM requests checksum manifests from downloads.wordpress.org/plugin-checksums/ using each plugin’s directory slug and installed version. These values are included in the request URL, along with normal connection metadata such as the server IP address. The plugin does not upload file contents, baseline hashes or finding paths to WordPress.org. Valid manifests are cached by slug and version for one day. WordPress.org service terms: https://wordpress.org/about/terms/ and privacy policy: https://wordpress.org/about/privacy/.
The request is sent when you run a manual scan, when a scheduled scan runs, or when the cached feed expires and the plugin needs a fresh copy. The request sends your configured Wordfence API key in the Authorization header and standard web request metadata from your server such as your server IP address and user agent. The plugin does not send your installed plugin/theme inventory, scan results, or site content to Wordfence.
Service provider: Defiant, Inc.
Terms of Service: https://www.wordfence.com/terms-of-service/
Privacy Policy: https://www.wordfence.com/privacy-policy/
Installation
- Upload
vulnerability-monitor-for-wordfence-intelligenceto the/wp-content/plugins/directory. - Activate the plugin through the Plugins menu.
- Open Security Scanner in the WordPress admin sidebar.
- Configure notification email, Wordfence API key, and preferred severity levels.
- (Optional) Enable scheduled scans.
FAQ
Does this plugin send my data to external servers?
The plugin fetches the Wordfence Intelligence feed from Wordfence.
It does not upload your installed plugin/theme inventory or scan results to Wordfence.
Does it slow down my website?
Scans run manually or through WP-Cron. File traversal can use CPU and disk I/O on large sites, and WP-Cron may start during a visitor request. Review the stated scan limits and verify performance on a non-production site before enabling scheduled scans.
Do I need a Wordfence account?
Yes. Wordfence Intelligence V3 requires an API key from your Wordfence account.
You can create it after signing in at the Integrations page in your Wordfence.com account.
Does this plugin store a default API key or email address?
No. The plugin does not ship with any embedded API key or hardcoded email address.
By default it uses your site’s existing admin_email setting until you change it.
Does this replace Wordfence?
No. This plugin is not a firewall.
It combines known vulnerability checks with local file integrity monitoring.
Can I customize the email template?
Yes! Both subject and body support placeholders like {site}, {count}, {time}, {list_html}.
Can agencies use this on client websites?
Absolutely. That’s one of the primary use cases.
Changelog
1.5.5
- Added explicit SHA-256 trust for extra .htaccess files in wp-admin and wp-includes.
- Added Update Trusted Hash for previously trusted uploads executables and extra core .htaccess files.
- Detects modified and deleted trusted core .htaccess files.
- Added scan-token validation to prevent trusting core files using stale scan results.
- Improved trusted-file removal persistence checks and regression coverage.
1.5.4
- Added configurable integrity scan exclusions for executable files in uploads.
- Added restricted glob pattern support, including WPML Twig cache paths.
- Excluded matching files from integrity findings, affected-file counts, and notifications.
- Displayed excluded files separately with a warning that they are not verified safe.
- Improved the Trusted uploads interface to clarify exclusion status.
- Added input validation, fail-open safeguards, and regression tests.
1.5.2
- Scaled uploads inspection beyond 100,000 ordinary files while retaining incomplete-scan and trusted-baseline protections.
- Accepted Core files matching either the installed locale or official English checksums for the same WordPress version.
- Recognized zero-byte uploads index.php placeholders.
- Moved visible FIM scheduling controls above the integrity overview and added a saved-state indicator.
1.5.1
- Fixed premature FIM notification emails by waiting for background plugin checksum verification to finish.
- Added an opt-in setting to include verified official plugin changes in FIM notifications. These changes are excluded by default.
- Preserved notifications for unverified changes, checksum mismatches, operational verification failures and .htaccess changes.
- Improved FIM notification counts, fingerprints and change detection when verified official plugin changes are excluded.
- Improved recovery from interrupted verification and WordPress Cron scheduling failures.
- Preserved FIM findings and manual trusted baseline acceptance.
1.5.0
- Added bounded, cached WordPress.org plugin checksum verification to background FIM scans.
- Added separate current-integrity classifications and plugin detail to FIM results and email.
- Redesigned the FIM dashboard, grouped findings, searchable monitoring scope and trusted baseline workflow.
- Added background verification status updates and clearer scan controls in the admin interface.
- Preserved every baseline change and manual baseline acceptance.
1.4.0
- Renamed the display and admin UI to Interaktiv Security Scanner; the plugin slug and saved settings remain unchanged.
- Added local file integrity monitoring, explicit trusted baselines, independently saved plugin/theme selection, official WordPress core checksums, uploads executable detection and summarized FIM notifications.
- Preserved the last successful vulnerability result when the feed is unavailable.
1.3.11
- Prevented false-positive theme alerts when a vulnerability feed omits a lower version bound for a newer major release line.
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
autoloaddisabled 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_newemail 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.
