CVE-2026-28361Medium▾ SunlitNocoDB Missing Ownership Validation in MCP Token Operations
▾ Sunlit zone — Low / medium · no exploitation signal
impact 27.5 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via GHSA
Last analysed / modified upstream
0.2%
The MCP token service did not validate token ownership, allowing a Creator within the same base to read, regenerate, or delete another user's MCP tokens if the token ID was known.
McpTokenService.get(), regenerateToken(), and delete() did not filter by fk_user_id. The analogous ApiTokensService correctly enforced ownership.
Limited — requires Creator role and knowledge of target token ID. Primary risk is denial of service (invalidating tokens) and scoped token disclosure.
This issue was reported by @bugbunny-research (bugbunny.ai).
nocodb <= 0.301.2Upgrade to a patched release:
nocodb 0.301.3Connected by shared product, vendor, weakness, or advisory.
CVE-2026-28396MediumNocoDB's Refresh Tokens Not Revoked on Password Reset
CVE-2026-28399MediumNocoDB Vulnerable to SQL Injection via DATEADD Formula
CVE-2026-28360LowNocoDB has Plaintext Storage of Shared View Passwords
CVE-2026-53927MediumNocoDB: Server-Side Request Forgery via Spreadsheet Fetch URL
CVE-2026-53928MediumNocoDB: Refresh Tokens Persist Through Password Recovery
CVE-2026-53929MediumNocoDB: Stored Cross-Site Scripting via Secure Attachment