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.

Ibrahim

Tessera is a developer library for plugin authors who register abilities via <code>wp_register_ability()</code> and want snapshot capture, audit logging, approval workflows, and one-click rollback for every invocation across REST, MCP, internal PHP, and WP-CLI without building it themselves.
Declare what state your ability touches; Tessera handles the safety wrapper.
<h4>What you get out of the box</h4>
<ul>
<li>Pre + post snapshots. Every safety-enabled invocation captures declared state before the callback and (on success) after, so the audit log can show a real diff.</li>
<li>Audit log. One row per invocation with ability name, caller (REST/MCP/CLI/internal), user, args, result, status, duration, pre/post hashes, and parent_invocation_id for nested calls.</li>
<li>One-click rollback. Restore captured state from post_meta, options, taxonomy term assignments, user roles + caps. File contents support tiered drift detection (mtime / mtime_size / critical_hash / full_hash) plus opt-in real byte-level rollback via <code>full_content</code> strategy.</li>
<li>Drift check on rollback. Live state is hashed and compared to the snapshot’s post-state before restoring; if they differ the rollback returns an error unless forced.</li>
<li>Concurrency lock. Capture + execute is serialised per surface set via a MySQL advisory lock so two simultaneous invocations do not capture each other’s mid-states.</li>
<li>Encrypted redaction. Scrub secrets out of args, results, and snapshots. Stores redacted values as AES-256-GCM envelopes so rollback can still restore them.</li>
<li>Approval queue. When <code>safety.requires_approval</code> is set, the wrapper blocks execution and returns a 202 pending response. A human approves or rejects via wp-admin, WP-CLI, or REST. Multi-stage sequential or parallel approval chains are supported.</li>
<li>Multisite support. Each subsite gets its own set of <code>wp_<N>_abilityguard_*</code> tables, with auto-install on <code>wp_initialize_site</code> and auto-drop on <code>wpmu_drop_tables</code>.</li>
<li>Retention. Daily WP-Cron prunes old log rows (defaults: 30 days normal, 180 days destructive) and orphaned snapshots.</li>
</ul>
<h4>Surfaces</h4>
<ul>
<li>PHP API with <code>wp_register_ability( $name, [ ..., 'safety' => [...] ] )</code> and helpers <code>abilityguard_rollback</code>, <code>abilityguard_snapshot_meta</code>, <code>abilityguard_snapshot_options</code>.</li>
<li>REST: <code>/abilityguard/v1/log</code>, <code>/log/<id></code>, <code>/log/export</code>, <code>/rollback/<id></code>, <code>/rollback/bulk</code>, <code>/approval</code>, <code>/approval/<id>/approve</code>, <code>/approval/<id>/reject</code>, <code>/approval/bulk</code>, <code>/approval/export</code>, <code>/retention</code>, <code>/retention/prune</code>, <code>/health</code>.</li>
<li>WP-CLI: <code>wp abilityguard log list/show</code>, <code>wp abilityguard rollback <id></code>, <code>wp abilityguard approval list/approve/reject <id></code>, <code>wp abilityguard prune</code>.</li>
<li>wp-admin: Tools > Tessera. Hybrid timeline + command-palette search, snapshot drawer, JSON-highlighted Input/Result tabs, invocation chain navigation, and real rollback against the captured snapshot.</li>
</ul>
<h4>Example</h4>
<pre><code>wp_register_ability( 'my-plugin/update-product-price', array(
 'label' => 'Update product price',
 'description' => 'Updates the price on a WooCommerce product.',
 'category' => 'woocommerce',
 'input_schema' => array( /* ... */ ),
 'permission_callback' => fn() => current_user_can( 'manage_woocommerce' ),
 'execute_callback' => fn( $args ) => update_post_meta( $args['product_id'], '_price', $args['price'] ),
 'safety' => array(
 'destructive' => true,
 'requires_approval' => false,
 'snapshot' => fn( $input ) => array(
 'post_meta' => array( $input['product_id'] => array( '_price', '_regular_price' ) ),
 'options' => array( 'woocommerce_last_price_change' ),
 ),
 ),
) );
</code></pre>
<h4>Documentation</h4>
Full plugin-author documentation lives at the GitHub repo: https://github.com/ibrahimhajjaj/abilityguard
<h3>Source Code</h3>
The full source for Tessera, including the unminified React source for the admin app, lives on GitHub: https://github.com/ibrahimhajjaj/abilityguard
<ul>
<li>The admin bundle <code>assets/admin.js</code> is compiled from <code>assets/admin.jsx</code> (React + JSX, no preprocessor magic beyond JSX).</li>
<li>The bundler is <a href="https://esbuild.github.io/" rel="nofollow ugc">esbuild</a>, configured in <code>scripts/build.mjs</code>.</li>
<li>To rebuild the admin bundle from a fresh checkout, run <code>npm install</code> once, then <code>npm run build</code> whenever <code>assets/admin.jsx</code> changes. This regenerates <code>assets/admin.js</code> in place.</li>
<li>The release zip published to the WordPress.org directory is produced by <code>scripts/build-release.sh</code>, which excludes development artifacts (tests, examples, build configs) but keeps everything required for the plugin to run.</li>
</ul>

Tessera for the Abilities API

Snapshot, audit, and rollback layer for plugins that register abilities via the WordPress Abilities API.

SudoWP Radar vs Tessera for the Abilities API