CyberRota Analysis
AI-GeneratedMCPHub versions prior to 1.0.32 are vulnerable due to inadequate role checking in their built-in prompt and resource controllers, allowing non-admin users to create, overwrite, and shadow global prompt templates and resources. This flaw can lead to unauthorized integrity violations, enabling attackers to tamper with records that affect all users, potentially resulting in stored prompt injection attacks in LLM sessions. Organizations using MCPHub should prioritize this vulnerability to mitigate risks associated with unauthorized access and data integrity breaches.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
MCPHub is a unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies. Prior to version 1.0.32, the built-in prompt and resource controllers perform no role checking. The mutating POST/PUT /api/prompts* and POST/PUT /api/resources* routes are attached to the authenticated router with no admin gate, and the handlers never read req.user. The DAO singletons they write are consulted first — ahead of any connected MCP server — for every session in handleGetPromptRequest / handleReadResourceRequest. A non-admin can therefore create, overwrite, and shadow global prompt templates and resources that all other users are served. The scored impact is the unauthorized integrity violation (creation/tampering/shadowing of globally-served records); stored prompt injection into other users' LLM sessions is a downstream consequence of that tampering. This issue has been patched in version 1.0.32.