| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| The GutenKit Blocks plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the /wp-json/gutenkit/v1/mailchimp/get/lists and /wp-json/gutenkit/v1/mailchimp/get/interests REST API endpoints in versions up to, and including, 2.4.12. Both endpoints are registered with permission_callback => '__return_true', and their callbacks read the site's stored Mailchimp API key from the gutenkit_settings_list option and proxy Mailchimp audience/list, merge-field, interest-category, interest-name, and subscriber-count metadata back to the caller with no login, nonce, or capability check. This makes it possible for unauthenticated attackers to retrieve private Mailchimp audience configuration information from any site that has configured the GutenKit Mailchimp integration. |
| The MountDev AI MCP Connector for WordPress plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.6.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to obtain an administrator-bound OAuth Bearer token via a self-registered client, granting full administrator-equivalent access to the plugin's MCP tool surface and all exposed WordPress content, users, and options. This is exploitable by combining the publicly accessible Dynamic Client Registration endpoint, which allows unauthenticated callers to register arbitrary OAuth clients with an attacker-controlled redirect_uri, with the unprotected authorization endpoint to complete the full OAuth flow without any administrator interaction. |
| Subscriber Broken Access Control in eRoom <= 1.7.1 versions. |
| Booking Agent Broken Access Control in QuickCal - Appointment Booking Calendar for WordPress <= 1.0.16 versions. |
| Unauthenticated Broken Access Control in MarketKing <= 2.1.40 versions. |
| Unauthenticated Broken Access Control in YT Player <= 2.0.9 versions. |
| Unauthenticated Broken Access Control in Autopay dla WooCommerce <= 2.2.27 versions. |
| Unauthenticated Broken Access Control in PayU India <= 3.8.9 versions. |
| Unauthenticated Broken Access Control in ShopLentor Pro <= 2.8.5 versions. |
| Subscriber Broken Access Control in ShopLentor Pro <= 2.8.5 versions. |
| Subscriber Broken Access Control in ЮKassa для WooCommerce <= 2.16.1 versions. |
| Unauthenticated Broken Access Control in Kit (formerly ConvertKit) <= 3.3.5 versions. |
| Subscriber Broken Access Control in Reviewer <= 3.14.2 versions. |
| Unauthenticated Broken Access Control in Content Control <= 2.6.5 versions. |
| Unauthenticated Broken Access Control in Event post <= 6.0.1 versions. |
| Unauthenticated Broken Access Control in Manual - Documentation, Knowledge Base & Education WordPress Theme <= 7.5.4 versions. |
| Contributor Broken Access Control in Avada Custom Branding <= 1.2 versions. |
| Unauthenticated Broken Access Control in Civi Framework <= 2.2.0 versions. |
| Subscriber Broken Access Control in Cyr to Lat reloaded – transliteration of links and file names <= 1.3.3 versions. |
| n8n before 2.29.8 and 2.30.x before 2.30.1 (affected from 2.27.0, when the OAuth 2.1 consent and token-issuance flow was introduced) does not verify that the authenticated user has access to the workflow referenced as the OAuth resource. On instances with at least one active MCP Server Trigger workflow configured with n8n OAuth2 authentication, a member-level user can register an OAuth client, self-approve consent for another user's workflow, and obtain a valid token. The workflow then runs in the owner's project context with the owner's stored credentials, and the attacker can set tool inputs and read outputs (potentially including data from the owner's connected integrations), breaking user and project isolation. |
