The report
An advisory for the WordPress AI Engine plugin describes OAuth Dynamic Client Registration in its MCP module accepting a client application without intended authorization. A related consent-page framing condition could then steer a user through a grant to a client with attacker-controlled redirect information. The vulnerable registration endpoint used an unguarded permission callback, and the reported affected releases extend through version 3.8.6.
The path depends on more than one condition. Registering a client is not the same as receiving an authorized token, and a valid token is not automatically a WordPress administrator session. The browser's consent interaction and the specific scopes issued determine the effect. The GitHub advisory identifies the registration and framing issues; the specific MCP investigation retains the prerequisite chain.
An operator should inspect whether dynamic registration is enabled, whether consent pages can be framed by another origin, and whether the token issuer binds client identity, redirect URI and scope to the intended user approval. The failure sits at the authorization layer that allows an assistant to invoke WordPress tools, not inside the text of a normal blog post.