Gerasimos

sudowp

SudoWP Radar is a runtime security auditor for the WordPress 6.9 Abilities API. It scans every registered ability across all active plugins and themes, applying a rule engine that detects the vulnerability patterns most likely to be exploited in production.
What it audits:
<ul>
<li>Open and weak permissions — abilities with no permission_callback, or one that allows any authenticated user through.</li>
<li>Missing or loose input schemas — abilities that accept unconstrained string inputs, creating potential injection vectors for path traversal, SSRF, and similar attacks.</li>
<li>REST overexposure — abilities marked show_in_rest with no or open permission control, accessible to unauthenticated callers.</li>
<li>MCP overexposure — abilities marked meta.mcp.public = true with a weak or null permission callback are directly callable by any connected AI agent. Flagged as CRITICAL.</li>
<li>Orphaned callbacks — execute_callbacks that reference functions no longer loaded, often left behind by deactivated plugins.</li>
<li>Namespace collisions — duplicate ability names where the last registration silently overwrites the first, potentially downgrading the permission model.</li>
<li>AI prompt filter bypass (WP 7.0+) — callbacks on wp_ai_client_prevent_prompt that unconditionally return false, disabling the AI prompt prevention gate sitewide. Flagged as HIGH.</li>
<li>AI REST overexposure (WP 7.0+) — REST endpoints that call wp_ai_client_prompt() with no or weak permission callbacks. Flagged as CRITICAL or HIGH.</li>
<li>AI missing version gate (WP 7.0+) — plugins that call wp_ai_client_prompt() without a function_exists compatibility check, causing fatal errors on WP < 7.0. Flagged as MEDIUM.</li>
<li>Hosting-injected ability (WP 7.0+) — abilities registered by hosting-provider auto-installed plugins with REST exposure, without explicit site administrator consent. Flagged as HIGH. Requires premium vendor slug list.</li>
<li>Connector key in database (WP 7.0+) — AI connector API keys stored as plaintext in the WordPress database via the WP 7.0 Connectors API, rather than as environment variables or PHP constants. Flagged as HIGH.</li>
</ul>
How it works:
SudoWP Radar reads the live abilities registry after all plugins and themes have loaded. It applies static rules to each ability and returns a structured findings report with severity ratings (Critical, High, Medium, Low) and actionable remediation guidance. A risk score from 0-100 summarises the overall exposure of the site.
Security model:
<ul>
<li>Requires the <code>radar_run_audit</code> capability (granted to site administrators by default).</li>
<li>All audit requests are nonce-gated. No public-facing endpoints.</li>
<li>Audit findings are stored in user meta, not global options.</li>
<li>Rate-limited to one audit per 30 seconds per user.</li>
</ul>
Optional premium extension (SudoWP Pro):
The free plugin is a fully functional standalone security auditor. An optional premium add-on extends it with SudoWP Vulnerability Dataset matching (CVE references, CVSS scores, patch guidance), scheduled audits with email alerts, multi-site dashboard aggregation, and report export. None of these are required to use the core auditing features.
SudoWP Radar is a complement to static analysis tools. It audits the live, runtime state of your site — what is actually registered and executing — not just what is declared in code.
<h3>External Services</h3>
When an API key is configured, SudoWP Radar connects to the SudoWP vulnerability 
dataset API (api.sudowp.com) to retrieve patch availability information for 
registered WordPress abilities.
No data is transmitted without an API key being explicitly entered by the site 
administrator. When no key is present, the plugin makes zero external network 
requests.
Data sent to the API: the ability name being looked up and your API key. 
No personal data, no site URL, no user data is transmitted.
API key registration: https://sudowp.com/get-api-key/ 
Terms of service: https://sudowp.com/tos/ 
Privacy policy: https://sudowp.com/privacy-policy/
<h3>Premium Extension Filters</h3>
SudoWP Radar exposes four WordPress filters so a premium plugin can extend 
the audit engine without modifying core plugin files.
<h4>radar_dataset_enabled</h4>
Controls whether dataset lookups run during an audit. Return true to activate.
Parameters: 
 $enabled (bool) — default false. 
 Returns: 
 bool
Example:
<pre><code>add_filter( 'radar_dataset_enabled', function ( bool $enabled ): bool {
 return true; // Enable dataset lookups.
} );
</code></pre>
<h4>radar_dataset_findings</h4>
Inject Finding objects from a vulnerability dataset for a specific ability. 
Called once per ability during an audit. Non-Finding return values are stripped.
Parameters: 
 $findings (array) — current Finding[] for this ability, default []. 
 $ability (array) — ability data array from Scanner (name, meta, callbacks, etc.). 
 Returns: 
 Finding[]
Note: register with accepted_args=2 to receive both parameters.
Example:
<pre><code>add_filter(
 'radar_dataset_findings',
 function ( array $findings, array $ability ): array {
 if ( str_starts_with( $ability['name'], 'my-plugin/' ) ) {
 $findings[] = new \SudoWP\Radar\Finding(
 ability_name: $ability['name'],
 severity: \SudoWP\Radar\Finding::SEVERITY_CRITICAL,
 vuln_class: \SudoWP\Radar\Finding::VULN_DATASET_MATCH,
 message: 'Known vulnerable ability pattern detected (CVE-2026-1234).',
 recommendation: 'Update my-plugin to version 2.1.0 or later.',
 is_premium: true,
 );
 }
 return $findings;
 },
 10,
 2
);
</code></pre>
<h4>radar_dataset_status</h4>
Override the dataset status array displayed in the admin UI.
Parameters: 
 $status (array) — default status with keys: 
 enabled (bool) — false in free version. 
 label (string) — UI display string. 
 last_updated (string|null) — ISO 8601 date or null. 
 total_entries (int) — 0 in free version. 
 Returns: 
 array (same shape as input)
Example:
<pre><code>add_filter( 'radar_dataset_status', function ( array $status ): array {
 return [
 'enabled' => true,
 'label' => 'SudoWP Vulnerability Dataset: Connected. 4,821 entries.',
 'last_updated' => '2026-03-08',
 'total_entries' => 4821,
 ];
} );
</code></pre>
<h4>radar_audit_findings</h4>
Modify the complete findings array after all rules and dataset lookups have run. 
Use this to add cross-ability findings, re-score existing findings, or suppress 
false positives. Called once per full audit run.
Parameters: 
 $findings (array) — complete Finding[] from the full audit. 
 $abilities (array) — all ability data arrays scanned during this audit. 
 Returns: 
 Finding[]
Note: register with accepted_args=2 to receive both parameters.
Example:
<pre><code>add_filter(
 'radar_audit_findings',
 function ( array $findings, array $abilities ): array {
 // Example: promote medium findings to high for a high-risk site.
 return array_map( function ( $finding ) {
 if ( $finding->severity === \SudoWP\Radar\Finding::SEVERITY_MEDIUM ) {
 return new \SudoWP\Radar\Finding(
 ability_name: $finding->ability_name,
 severity: \SudoWP\Radar\Finding::SEVERITY_HIGH,
 vuln_class: $finding->vuln_class,
 message: $finding->message,
 recommendation: $finding->recommendation,
 context: $finding->context,
 is_premium: $finding->is_premium,
 );
 }
 return $finding;
 }, $findings );
 },
 10,
 2
);
</code></pre>

SudoWP Radar

Security auditor for the WordPress Abilities API. Scans registered abilities for permission, schema, and exposure risks.

miniOrange

miniOrange Secure MCP Server helps WordPress administrators with AI governance and policy enforcement: understanding, and controlling, what AI assistants and MCP clients are allowed to do on their site.
The WordPress Abilities API (available in WordPress 6.9 and later) lets plugins and WordPress core expose discrete, machine-callable capabilities — for example: get site info, create a post, or generate a summary. This plugin turns those abilities into a remote Model Context Protocol (MCP) server so AI clients can discover and invoke them, protected by a self-hosted OAuth 2.1 authorization server.
What this version does
<ul>
<li>Abilities viewer. A read-only admin screen (in the Secure MCP Server menu) that lists every ability registered on your site, with its label, description, category, source namespace, and full input/output JSON schema.</li>
<li>Connection guide. A “Connect to AI” tab with step-by-step instructions and your site’s MCP URL for connecting clients such as ChatGPT and Claude.</li>
<li>Built-in content abilities. Create Post and Update Post abilities (exposed as MCP tools) so connected clients can draft and edit posts, gated by the user’s capabilities.</li>
<li>MCP server. A single Streamable HTTP endpoint that exposes every registered ability as an MCP tool. Tool calls run through the Abilities API, so each ability’s own permission check still applies.</li>
<li>Self-hosted dynamic OAuth. WordPress acts as its own OAuth 2.1 authorization server with OAuth 2.0 Dynamic Client Registration (RFC 7591), Protected Resource Metadata (RFC 9728), Authorization Server Metadata (RFC 8414), and Authorization Code flow with PKCE. Clients such as ChatGPT and Claude can register themselves and connect with no manual credential setup.</li>
</ul>
Every MCP request runs as the WordPress user who authorized it, so what an AI client can do is bounded by that user’s own capabilities.

miniOrange Secure MCP Server

AI governance for WordPress: expose your Abilities API as a secure, OAuth-protected MCP server for AI clients like ChatGPT and Claude.

SudoWP Radar vs miniOrange Secure MCP Server