Description

Missing Authorization vulnerability in Cascadia Web Services MountDev AI MCP Connector for WordPress allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects MountDev AI MCP Connector for WordPress: from n/a through 1.6.5.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.5",
  "pubDate": "2026-09-03T17:17:30.833Z",
  "pubdate": "2026-09-03T17:17:30.833Z",
  "executiveSummary": "The MountDev AI MCP Connector for WordPress is susceptible to a Missing Authorization vulnerability, classified under CWE-862 (Missing Authorization).\nThe flaw allows unauthorized users to interact with plugin functionality due to improperly configured access control security levels.\nThe vulnerability affects all versions of the product from n/a through 1.6.5.\nBy failing to implement robust access control checks on critical API endpoints or administrative functions, the plugin enables attackers to perform unauthorized actions without legitimate authentication or elevated privileges.\nThe primary risk implication involves potential manipulation of plugin settings, unauthorized data access, or service disruption within the WordPress environment.\nExploitation does not require prior administrative authentication, making it accessible to remote unauthenticated attackers who can reach the plugin’s exposed endpoints.\nThis vulnerability highlights a critical failure in enforcing authorization policies during request processing, potentially exposing internal MCP (Model Context Protocol) configurations or connector functionalities to malicious actors.",
  "technicalDetails": "The root cause of the vulnerability lies in the insufficient enforcement of authorization checks within the plugin's request handling logic. The MountDev AI MCP Connector fails to adequately validate the privileges of the requester before executing sensitive operations associated with the Model Context Protocol (MCP) integration.\nWhen a request is submitted to the plugin’s endpoints, the application logic does not perform a robust verification against the current user’s session or defined WordPress roles. Consequently, the system assumes that any incoming request is authorized, effectively bypassing intended security constraints designed to restrict access based on user authorization levels.\nThe exploitation flow typically begins with an attacker identifying the endpoint responsible for MCP connector operations. Since the component lacks granular authorization checks, an attacker can send crafted HTTP requests to these endpoints without providing valid authentication tokens or holding administrative permissions.\nOnce the request reaches the vulnerable component, the backend processes the instructions dictated by the payload because the internal access control gates are missing or improperly configured. This permits an attacker to interface with the connector's internal mechanisms, potentially modifying sensitive configurations, exfiltrating connector data, or triggering unauthorized AI-driven backend interactions.\nThe attack is characterized by its ability to execute logic reserved for authenticated or privileged users by simply omitting the standard security handshakes. Because the vulnerability is inherent to the plugin's code architecture rather than a configuration error by the end-user, it persists across all installations using affected versions (n/a through 1.6.5).\nPost-exploitation, the impact is significant, as it grants an unauthenticated entity the ability to influence the behavior of the AI connector. If the connector possesses high-level permissions within the WordPress installation or linked external services, an attacker could leverage this lack of authorization to perform lateral movement or conduct further attacks on the WordPress infrastructure. The lack of proper privilege validation constitutes a total breakdown of the plugin’s security model regarding its interface management."
}