videowhisper

VideoWhisper Security Audit creates WordPress site health, exposure, vulnerability, integrity, readiness, and performance reports for site administrators. The plugin is designed to help administrators review site activity and configuration with AI agents or by using the built-in admin report.
The free plugin is read-only. It reports findings and does not perform cleanup, quarantine, updates, file changes, role changes, or other remediation actions.
Main features:
<ul>
<li>Admin Scan tab with scan mode selector, cooldown-aware Run Scan button, scan date, report summary, and report findings.</li>
<li>Importance-based scan modes: full, critical/high/medium, and critical-only.</li>
<li>Report filters for issues only or all check results, including passed informational checks when available.</li>
<li>JSON and plain-text Markdown report output.</li>
<li>Optional token-protected REST report endpoint.</li>
<li>Optional token-protected MCP endpoint for read-only AI-agent reports.</li>
<li>Read-only integration with <a href="https://wordpress.org/plugins/videowhisper-site-manager/" rel="ugc">VideoWhisper AI Site Manager – Using ChatGPT Claude Codex</a> when both plugins are active.</li>
<li>Separate REST and MCP enable/disable settings.</li>
<li>Generated local tokens with rotation controls and last-used metadata.</li>
<li>REST/MCP per-minute rate limiting and optional exact IP allowlist.</li>
<li>Admin scan cooldown, hourly scan limit, and separate agent scan cooldown.</li>
<li>Category toggles for security, integrity, performance, readiness, commerce, community, and backup checks.</li>
<li>Redacted AI report defaults, with optional exact version and path disclosure for MCP reports.</li>
<li>Optional WPVulnerability API lookups for installed plugin vulnerability data.</li>
<li>Disclaimers in the admin report and Agents tab about report limits, sensitive information, and third-party AI analysis.</li>
</ul>
<h4>Local checks</h4>
Security Audit currently checks local WordPress signals including:
<ul>
<li>Plugin and theme updates.</li>
<li>Inactive plugins.</li>
<li>Administrator account count.</li>
<li>Expected WordPress database tables.</li>
<li>Administrator role capabilities.</li>
<li>Upload directory writability.</li>
<li>Debug log file presence.</li>
<li>Git metadata in the web root.</li>
<li>XML-RPC availability.</li>
<li>Common homepage security headers.</li>
<li>Autoloaded option size.</li>
<li>Expired transient count.</li>
<li>WP-Cron disabled state.</li>
<li>Permalink structure.</li>
<li>Search engine visibility setting.</li>
<li>Privacy Policy page presence.</li>
<li>Basic WooCommerce page readiness when WooCommerce is active.</li>
<li>Optional WPVulnerability plugin vulnerability lookups.</li>
</ul>
<h4>Agent and API reports</h4>
REST and MCP endpoints are disabled by default. When enabled, Security Audit automatically generates local tokens. Anyone with a valid token can read the selected report until the token is rotated, so treat tokens as sensitive secrets.
The REST report endpoint supports:
<ul>
<li><code>key</code>: generated REST token. A bearer token can also be used.</li>
<li><code>mode</code>: <code>full</code>, <code>important</code>, <code>critical</code>, or <code>changed</code>.</li>
<li><code>report</code>: <code>issues</code> or <code>all</code>.</li>
<li><code>format</code>: omit for JSON, or use <code>markdown</code> for plain Markdown output.</li>
</ul>
The MCP endpoint supports read-only tools for security summary, vulnerability, exposure, integrity, performance risk, readiness, and Markdown audit reports. Tool arguments include <code>mode</code> and <code>report</code>.
Endpoint protection controls include:
<ul>
<li>REST/MCP requests per minute per IP.</li>
<li>Separate agent scan cooldown.</li>
<li>Optional exact IPv4/IPv6 allowlist.</li>
<li>Token rotation.</li>
</ul>
<h4>Important limitations and disclaimers</h4>
Security Audit reports are informational only. Findings and AI-ready reports may be incomplete, inaccurate, outdated, or unsuitable for a specific site or legal situation.
Security Audit does not provide legal advice, compliance certification, professional security advice, malware cleanup, incident response, or a guarantee that a site is secure. Administrators should verify findings and consult an experienced security, technical, or legal provider before making important changes.
REST and MCP reports may expose sensitive operational information, including site configuration, component versions, possible vulnerabilities, paths, and other details. Enable agent endpoints only when you understand where the data will be sent and who can access the token.
Third-party AI agents may produce incomplete, incorrect, unsafe, or unsuitable recommendations. Review all recommendations before acting and do not perform destructive changes without backups and appropriate professional review.
This plugin is not a firewall, malware cleaner, legal compliance tool, vulnerability scanner guarantee, or replacement for backups, security monitoring, dedicated scanners, or experienced administrators.
<h4>External services</h4>
By default, Security Audit does not call external vulnerability services.
If the administrator enables WPVulnerability lookups, the plugin sends installed plugin slugs to the public WPVulnerability API at <code>https://www.wpvulnerability.net/</code> to retrieve vulnerability data. No API key is required for normal component lookups. Responses are cached locally. See:
<ul>
<li>https://www.wpvulnerability.com/</li>
<li>https://docs.wpvulnerability.com/</li>
<li>https://www.wpvulnerability.com/privacy/</li>
<li>https://www.wpvulnerability.com/license/</li>
</ul>
During scans, Security Audit may also make a local HTTP HEAD request to the site’s own homepage URL to inspect response headers. This request is sent to the configured site URL, not to a third-party vulnerability service.

VideoWhisper Security Audit

AI-ready WordPress site health and security reports for administrators, with optional read-only REST and MCP access.

Guido Schad

Lockora Security Audit helps site owners and agencies review a WordPress site’s security posture from the admin area.
Current prototype features include:
<ul>
<li>Manual security scans.</li>
<li>Weighted security score out of 100.</li>
<li>WordPress core file integrity checks using official checksums.</li>
<li>WordPress authentication key and salt checks, with an explicit action to generate missing salts.</li>
<li>Must-use plugin directory presence checks.</li>
<li>PHP version status using WordPress.org Serve Happy data.</li>
<li>HTTPS and HTTP security header checks.</li>
<li>WordPress core, plugin, and theme update posture checks.</li>
<li>Administrator account posture checks for default usernames, excess admins, inactive admins, user ID 1 exposure, and an admin username/email inventory.</li>
<li>Optional known vulnerability matching with a configured Wordfence Intelligence API key.</li>
<li>Optional AI client reports on WordPress 7.0+ when the site’s AI Connector is configured.</li>
<li>Reversible hardening toggles for XML-RPC, REST user routes, generator tag output, and basic security headers.</li>
</ul>
<h3>External Services</h3>
Lockora Security Audit may connect to external services only when the administrator runs a scan or generates an AI client report.
WordPress.org APIs: 
* Used for WordPress core checksums, PHP version support status, and WordPress core/plugin/theme update data. 
* Data sent: the site’s WordPress version and locale for core checksums and PHP compatibility; WordPress itself may send installed plugin and theme slugs/versions to WordPress.org when update data is refreshed. 
* WordPress.org terms: https://wordpress.org/about/terms/ 
* WordPress.org privacy policy: https://wordpress.org/about/privacy/
Wordfence Intelligence: 
* Optional. 
* Used only when a Wordfence Intelligence API key is configured and an administrator runs a scan that includes vulnerability matching. 
* Used to retrieve vulnerability data and match it locally against installed WordPress core, plugin, and theme versions. 
* Data sent: the configured Wordfence Intelligence API key is sent in an Authorization header when requesting the vulnerability feed. Installed software details are not sent by this plugin to the Wordfence Intelligence endpoint; matching is performed locally after the feed is retrieved. 
* Wordfence Intelligence terms: https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/ 
* Wordfence privacy policy: https://www.wordfence.com/privacy-policy/
WordPress AI Client / Connectors: 
* Optional. 
* Used only when the administrator clicks Generate Client Report. 
* Data sent: sanitized scan findings, score, counts, and recommendations needed to generate a client-facing report. The plugin is designed not to send passwords, salts, API keys, raw logs, full user lists, or file contents. 
* The configured AI provider is controlled by the site owner’s WordPress Connector settings. 
* Terms and privacy policy: these depend on the AI provider configured by the site owner in WordPress. Site owners should review the selected provider’s terms and privacy policy before enabling AI reports.

Lockora Security Audit

Lockora Security Audit checks WordPress security posture, hardening, core integrity, vulnerabilities, and optional AI reports.

VideoWhisper Security Audit vs Lockora Security Audit