VMP™

<h4>COMPREHENSIVE WORDPRESS SECURITY SCANNER</h4>
VMP Fence Security provides protection for WordPress websites through an advanced multi-scanner architecture. Our plugin features 11 specialized security scanners that work together to detect malware, vulnerabilities, suspicious activities, and security threats.
VMP Fence Security includes malware detection, file integrity monitoring, vulnerability scanning, user security analysis, and comprehensive threat protection.
<h3>🛡️ MULTI-SCANNER SECURITY ARCHITECTURE</h3>
<ul>
<li>Server State Scanner monitors server configuration and security settings</li>
<li>File Changes Scanner detects unauthorized modifications to WordPress core, themes, and plugins </li>
<li>User Security Scanner identifies suspicious user accounts, risky usernames, and admin enumeration</li>
<li>Content Safety Scanner analyzes posts and comments for malicious content and URLs</li>
<li>Public Files Scanner checks for exposed configuration files and sensitive data</li>
<li>User Audit Scanner monitors user activities and permission changes</li>
<li>Vulnerability Scanner identifies known security vulnerabilities in installed plugins and themes</li>
<li>Malware Scanner detects malicious code, backdoors, and infected files</li>
<li>Domain Blocklist Scanner checks against known malicious domains and reputation databases</li>
<li>Spamvertising Scanner identifies spam content injection and SEO spam attacks</li>
<li>IP Spam Scanner monitors for suspicious IP addresses and bot activity</li>
</ul>
<h3>🔍 MALWARE DETECTION & FILE SCANNING</h3>
<ul>
<li>Advanced malware signatures with pattern-based detection for backdoors and trojans</li>
<li>File integrity monitoring compares files against WordPress.org repository versions</li>
<li>Binary file scanning detects malicious code in images and executables</li>
<li>WordPress core verification ensures core files haven’t been tampered with</li>
<li>Plugin and theme scanning identifies modified or infected extensions</li>
<li>Unknown file detection flags suspicious files that don’t belong to WordPress</li>
</ul>
<h3>🚨 VULNERABILITY & THREAT DETECTION</h3>
<ul>
<li>Plugin vulnerability scanning checks for known security issues in installed plugins</li>
<li>Theme vulnerability detection identifies security flaws in active themes</li>
<li>WordPress core vulnerabilities monitors for outdated WordPress installations</li>
<li>Google Safe Browsing integration checks URLs against Google’s malware database</li>
<li>Suspicious admin detection identifies potentially compromised administrator accounts</li>
<li>Password security analysis detects weak or compromised passwords</li>
</ul>
<h3>⚙️ SCAN CONFIGURATION & MANAGEMENT</h3>
<ul>
<li>Multiple scan types: Limited (quick), Standard (balanced), High Sensitivity (comprehensive), Custom (configurable)</li>
<li>Scheduled scanning with flexible timing options (hourly, daily, weekly)</li>
<li>Scan monitoring system with automatic recovery from interrupted scans</li>
<li>Performance optimization with memory management and resource controls</li>
<li>File exclusion patterns to customize scanning scope and reduce false positives</li>
<li>Progress tracking with real-time status updates and detailed logging</li>
</ul>
<h3>📊 ADMIN INTERFACE & REPORTING</h3>
<ul>
<li>Dashboard overview showing security status and recent scan results</li>
<li>Detailed scan results with issue classification and remediation guidance</li>
<li>Audit logging tracks all security events and user activities</li>
<li>Scan result reporting with detailed security issue analysis and remediation guidance</li>
<li>Activity logs accessible via “Show Log” and “See Full Log” interface buttons</li>
<li>Issue management with options to ignore detected threats or repair infected files</li>
</ul>
<h3>🔧 ADVANCED FEATURES</h3>
<ul>
<li>API integrations including Google Safe Browsing for URL reputation checking</li>
<li>Background processing prevents timeouts during large site scans</li>
<li>Resource management with configurable memory limits and execution timeouts</li>
<li>IPv4/IPv6 support with option to force IPv4-only scanning</li>
<li>Multi-site compatibility works with WordPress multisite installations</li>
<li>Flexible configuration with comprehensive options and settings management</li>
</ul>
<h3>Privacy and Data Collection</h3>
VMP Fence respects your privacy and follows WordPress.org guidelines for external service usage. This plugin may collect and transmit data to external services for security analysis:
Google Safe Browsing API: When URL reputation checking is enabled, URLs found in your content, posts, comments, and uploaded files are sent to Google’s Safe Browsing service to check against databases of malicious websites, phishing sites, and malware distribution points. This helps protect your site from security threats.
Data sent to Google includes: 
– URLs extracted from posts, pages, comments, and file content 
– Website URLs being analyzed for reputation 
– No personal information, user data, or site content is transmitted beyond the URLs themselves
Data NOT sent to Google: 
– User personal information or login credentials 
– Post content, comment text, or page content 
– Database information or configuration details 
– User behavior or analytics data
Your Privacy Rights: 
– In the current version (1.0.0), Google Safe Browsing integration is enabled by default for security protection 
– Future plugin updates will include user settings to disable external service usage 
– No data is collected or stored by VMP Fence itself beyond standard WordPress security logs
Third-Party Privacy Policies: 
– Google Safe Browsing API: https://developers.google.com/safe-browsing/v4/usage-limits 
– Google Privacy Policy: https://policies.google.com/privacy
Data Retention: 
VMP Fence caches URL reputation results locally for up to 1 hour to improve performance and reduce external API calls. These cached results are stored only on your server and are automatically purged.
Current Limitation: 
In version 1.0.0, Google Safe Browsing integration is automatically enabled for URL scanning. Future versions will include user settings to control external service usage. If you prefer not to use external services, please contact the plugin developer or wait for the next update which will include privacy controls.
<h3>GitHub WordPress Repository (File Comparison/Diff Viewer)</h3>
Service Purpose: 
VMP Fence connects to GitHub’s raw content service to download original WordPress core files for displaying file differences/comparisons in the admin interface.
Service URLs: 
– Primary: https://raw.githubusercontent.com/WordPress/ 
– Fallback: https://core.svn.wordpress.org/
When This Service Is Called: 
– Only when user clicks “View Differences” button on a scan result 
– Used to show side-by-side comparison of current file vs original WordPress core file 
– NOT called during regular scanning operations or automated processes
Data Sent to GitHub: 
– WordPress version number (e.g., “6.8”) 
– File path relative to WordPress root (e.g., “wp-admin/index.php”) 
– HTTP User-Agent header: “VMPFence Security Scanner” 
– NO personal data, user information, site content, or configuration details are sent
Data Received from GitHub: 
– Original WordPress core file content for comparison and repair 
– Public repository data only (no tracking or analytics)
Privacy Implications: 
– GitHub may log standard web server access logs (IP address, user agent, timestamp) 
– No authentication required – all accessed files are public WordPress core files 
– No data is collected or stored by VMP Fence beyond the file content used for verification
Required: 
– Optional feature – viewing file differences can be skipped 
– Internet connection required only when viewing file comparisons 
– Regular security scanning does not require this service
Third-Party Privacy Policy: 
– GitHub Privacy Statement: https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement
User Control: 
– This feature is only activated when user manually clicks “View Differences” button 
– No automatic background requests are made 
– Users can review scan results without using this feature

VMP Fence Security

Advanced WordPress security plugin with comprehensive malware scanner, vulnerability detection, and multi-layer protection system.

David Perez

Javier Casares

Close·technology

Alex Lion (阿力獅)

Lucas Bonomo

This plugin integrates with the WPVulnerability API to provide real-time vulnerability assessments for your WordPress core, plugins, themes, PHP version, Apache HTTPD, nginx, MariaDB, MySQL, ImageMagick, curl, memcached, Redis, and SQLite.
It delivers detailed reports directly within your WordPress dashboard, helping you stay aware of potential security risks. Configure the plugin to send periodic notifications about your site’s security status, ensuring you remain informed without being overwhelmed. Designed for ease of use, it supports proactive security measures without storing or retrieving any personal data from your site.
<h4>Data reliability</h4>
The information provided by the information database comes from different sources that have been reviewed by third parties. There is no liability of any kind for the information. Act at your own risk.
<h3>Using the plugin</h3>
<h4>WP-CLI</h4>
You can use the following WP-CLI commands to manage and check vulnerabilities:
<ul>
<li>Core: <code>wp wpvulnerability core</code></li>
<li>Plugins: <code>wp wpvulnerability plugins</code></li>
<li>Themes: <code>wp wpvulnerability themes</code></li>
<li>PHP: <code>wp wpvulnerability php</code></li>
<li>Apache HTTPD: <code>wp wpvulnerability apache</code></li>
<li>nginx: <code>wp wpvulnerability nginx</code></li>
<li>MariaDB: <code>wp wpvulnerability mariadb</code></li>
<li>MySQL: <code>wp wpvulnerability mysql</code></li>
<li>ImageMagick: <code>wp wpvulnerability imagemagick</code></li>
<li>curl: <code>wp wpvulnerability curl</code></li>
<li>memcached: <code>wp wpvulnerability memcached</code></li>
<li>Redis: <code>wp wpvulnerability redis</code></li>
<li>SQLite: <code>wp wpvulnerability sqlite</code></li>
</ul>
To configure the plugin you can use:
<ul>
<li>Hide component: <code>wp wpvulnerability config hide <component> [on|off]</code></li>
<li>Notification email: <code>wp wpvulnerability config email <emails></code> (comma separatted)</li>
<li>Notification period: <code>wp wpvulnerability config period <never|daily|weekly></code></li>
<li>Log retention: <code>wp wpvulnerability config log-retention <0|1|7|14|28></code> (in days)</li>
<li>Cache duration: <code>wp wpvulnerability config cache <1|6|12|24></code> (in hours)</li>
</ul>
All commands support the <code>--format</code> option to specify the output format:
<ul>
<li><code>--format=table</code>: Displays the results in a table format (default).</li>
<li><code>--format=json</code>: Displays the results in JSON format.</li>
</ul>
Need help?
<ul>
<li><code>wp wpvulnerability --help</code>: Displays help information for WPVulnerability commands.</li>
<li><code>wp wpvulnerability [command] --help</code>: Displays help information for a WPVulnerability command.</li>
</ul>
<h4>REST API</h4>
The WPVulnerability plugin provides several REST API endpoints to fetch vulnerability information for different components of your WordPress site.
<ul>
<li>Core: <code>/wpvulnerability/v1/core</code></li>
<li>Plugins: <code>/wpvulnerability/v1/plugins</code></li>
<li>Themes: <code>/wpvulnerability/v1/themes</code></li>
<li>PHP: <code>/wpvulnerability/v1/php</code></li>
<li>Apache HTTPD: <code>/wpvulnerability/v1/apache</code></li>
<li>nginx: <code>/wpvulnerability/v1/nginx</code></li>
<li>MariaDB: <code>/wpvulnerability/v1/mariadb</code></li>
<li>MySQL: <code>/wpvulnerability/v1/mysql</code></li>
<li>ImageMagick: <code>/wpvulnerability/v1/imagemagick</code></li>
<li>curl: <code>/wpvulnerability/v1/curl</code></li>
<li>memcached: <code>/wpvulnerability/v1/memcached</code></li>
<li>Redis: <code>/wpvulnerability/v1/redis</code></li>
<li>SQLite: <code>/wpvulnerability/v1/sqlite</code></li>
</ul>
The WPVulnerability REST API uses Application Passwords for authentication. You need to include a valid Application Password in the Authorization header of your requests.
Example Request with Authentication
<pre><code>curl -X GET https://example.com/wp-json/wpvulnerability/v1/plugins -u username:application_password
</code></pre>
Replace username with your WordPress <code>username</code> and <code>application_password</code> with your <a href="https://make.wordpress.org/core/2020/11/05/application-passwords-integration-guide/" rel="nofollow ugc">Application Password</a>.
<h3>Extra Configurations</h3>
<h4>“From:” mail (since: 3.2.2)</h4>
If, for some reason, you need the emails sent by the plugin to have a From different from the site administrator, you can change it from the <code>wp-config.php</code> by adding a constant:
<pre><code>define( 'WPVULNERABILITY_MAIL', 'sender@example.com' );
</code></pre>
If the constant is active, it will be visible in the configuration screen.
<h4>Force hiding checks (since: 4.1.0)</h4>
If you want to always hide a specific component, you can define a constant in <code>wp-config.php</code>. When set to <code>true</code>, the option will be checked automatically in the settings screen and the related analysis will be skipped.
Example:
<pre><code>define( 'WPVULNERABILITY_HIDE_APACHE', true );
</code></pre>
Available constants: <code>WPVULNERABILITY_HIDE_CORE</code>, <code>WPVULNERABILITY_HIDE_PLUGINS</code>, <code>WPVULNERABILITY_HIDE_THEMES</code>, <code>WPVULNERABILITY_HIDE_PHP</code>, <code>WPVULNERABILITY_HIDE_APACHE</code>, <code>WPVULNERABILITY_HIDE_NGINX</code>, <code>WPVULNERABILITY_HIDE_MARIADB</code>, <code>WPVULNERABILITY_HIDE_MYSQL</code>, <code>WPVULNERABILITY_HIDE_IMAGEMAGICK</code>, <code>WPVULNERABILITY_HIDE_CURL</code>, <code>WPVULNERABILITY_HIDE_MEMCACHED</code>, <code>WPVULNERABILITY_HIDE_REDIS</code>, <code>WPVULNERABILITY_HIDE_SQLITE</code>.
<h4>Cache duration (since: 4.1.0)</h4>
By default, data from the API is cached for 12 hours.
<pre><code>define( 'WPVULNERABILITY_CACHE_HOURS', 24 );
</code></pre>
To change this, define <code>WPVULNERABILITY_CACHE_HOURS</code> in <code>wp-config.php</code> with one of <code>1</code>, <code>6</code>, <code>12</code> or <code>24</code>. This value overrides the setting screen and WP-CLI command.
<h4>Log rotation (since: 4.2.0)</h4>
WPVulnerability stores the most recent API responses so you can review recent calls from the new log tab. Define <code>WPVULNERABILITY_LOG_RETENTION_DAYS</code> in <code>wp-config.php</code> to control how many days of entries are preserved. Supported values are <code>0</code>, <code>1</code>, <code>7</code>, <code>14</code> or <code>28</code>; using <code>0</code> disables logging entirely.
<pre><code>define( 'WPVULNERABILITY_LOG_RETENTION_DAYS', 14 );
</code></pre>
When the constant is present its value is enforced in the settings UI and through WP-CLI, ensuring consistent log rotation across environments.
<h3>Compatibility</h3>
<ul>
<li>WordPress: 4.7 – 6.9</li>
<li>PHP: 5.6 – 8.4</li>
<li>WP-CLI: 2.3.0 – 2.11.0</li>
</ul>
<h3>Security</h3>
This plugin adheres to the following security measures and review protocols for each version:
<ul>
<li><a href="https://developer.wordpress.org/plugins/" rel="nofollow ugc">WordPress Plugin Handbook</a></li>
<li><a href="https://developer.wordpress.org/plugins/wordpress-org/plugin-security/" rel="nofollow ugc">WordPress Plugin Security</a></li>
<li><a href="https://developer.wordpress.org/apis/security/" rel="nofollow ugc">WordPress APIs Security</a></li>
<li><a href="https://github.com/WordPress/WordPress-Coding-Standards" rel="nofollow ugc">WordPress Coding Standards</a></li>
<li><a href="https://wordpress.org/plugins/plugin-check/" rel="ugc">Plugin Check (PCP)</a></li>
<li><a href="https://www.sonarsource.com/products/sonarcloud/" rel="nofollow ugc">SonarCloud Code Review</a></li>
</ul>
<h3>Privacy</h3>
<ul>
<li>This plugin or the WordPress Vulnerability Database API does not collect any information about your site, your identity, the plugins, themes or content the site has.</li>
</ul>
<h3>Vulnerabilities</h3>
<ul>
<li>No vulnerabilities have been published up to version 4.2.0.</li>
</ul>
Found a security vulnerability? Please report it to us privately at the <a href="https://github.com/javiercasares/wpvulnerability/security/advisories/new" rel="nofollow ugc">WPVulnerability GitHub repository</a>.
<h3>Contributors</h3>
You can contribute to this plugin at the <a href="https://github.com/javiercasares/wpvulnerability" rel="nofollow ugc">WPVulnerability GitHub repository</a>.

WPVulnerability

Without sending data, as other plugins does, the best way to detect vulnerabilities without privacy concerns.

The best way to detect vulnerabilities, and free!

Fácil de instalar y configurar y de gran utilidad para detectar vulnerabilidades en nuestro WordPress. Totalmente recomendable. 

Imprescindible para toda web

Gracias por el plugin. 

Ya puedo estar informado fácilmente de las vulnerabilidades de mi web.

Lo mejor para estar informado de las vulnerabilidades de tu WordPress

This plugin uses an API to check if the version of your core, themes and/or plugins present on your WordPress installation has any known vulnerability.

It cares about efficiency so it can be always active, it won't have any noticeable affection to the load time of the public website (it only connects to the api when an administrator installs/updates something and also via cron each several hours).

I can recommend to have this plugin active to help you spot possible vulnerabilities when forgot or delayed the update of plugin/theme/core. 

A great aid for detecting vulnerabilities.


Without a doubt, the most important plugin to install on your WordPress instance.


Essential plugin

Get WordPress vulnerability alerts from the WPVulnerability Database API.

VMP Fence Security vs WPVulnerability