Ent Companion WP Registry grade C-. High-severity findings · 1 findingWP RegistryHigh-severity findings · 1 findingOpen the reportC-

High-severity findings.

Audited release

2.2.0

Findings

1

Worst severity

high

Content hash

4c2a66473680e1d4b2e26269… Copy

Findings

• high Editor can create and activate arbitrary PHP snippets via MCP abilities

  rce

  All seven snippet abilities (list/get/create/update/activate/deactivate/verify) use permission_callback EC_Permissions::can_manage_snippets, which is only current_user_can('unfiltered_html'). The inline comment claims this matches FluentSnippets REST; FluentSnippets actually requires install_plugins AND unfiltered_html for create/edit, and Code Snippets defaults to manage_options (code_snippets_cap). On a default single-site WordPress install, the Editor role has unfiltered_html and lacks both install_plugins and manage_options, so Editors are blocked in those UIs but allowed here. The abilities are mcp.public, so MCP Adapter's default server will list and execute them for any authenticated user who passes the ability callback (default MCP transport is logged-in + read). Execute paths call FluentSnippets\App\Helpers\Helper::createSnippet / updateSnippet / Snippet::updateSnippet and Code Snippets DB add/update/save with no second capability check. validate_ability_snippet_code only requires the PHP string to mention wp_abilities_api_init and a register helper; arbitrary PHP can be smuggled alongside those tokens. Observable: POST MCP tools/call execute-ability ability_name=ent-companion/snippets-create with name+code, then snippets-activate; a published PHP file appears under the FluentSnippets storage dir (or an active Code Snippets row) and runs on subsequent front-end/admin requests. Subscriber/Author/unauth are stopped. Administrators already have this power by design.

  includes/class-permissions.php:76-81

  Recommendation

  Require the same capabilities the snippet backends use: current_user_can('install_plugins') && current_user_can('unfiltered_html') when FluentSnippets is the provider, and current_user_can(code_snippets()->get_cap()) (default manage_options) when Code Snippets is the provider. Do not treat unfiltered_html alone as sufficient for writing executable PHP. Keep create as draft-only and require the tightened cap on activate/update as well.

WP Registry hashes the installable build and reports on that exact bytes-for-bytes copy. Embargoed findings are withheld until they are disclosed, so a clean verdict means nothing public is outstanding. WP Manifest does not audit code itself.