The vulnerability exists in NocoDB’s MCP token service, where token ownership validation is missing. A user with the Creator role in a base can read, regenerate, or delete any other user’s MCP token if the token ID is known. This flaw allows an attacker to manipulate tokens that they do not own, potentially changing authentication credentials or revoking access for other users. The weakness is mapped to CWE-639, which represents lack of ownership checks on resource operations.

NocoDB version 0.301.2 and earlier. The issue persists until version 0.301.3, which includes the ownership validation fix. The affected product is NocoDB, a web‑based spreadsheet‑to‑database platform.

The CVSS rating of 4.9 indicates low severity, and the EPSS score is reported as below 1 % so the probability of exploitation is very low. The flaw is not listed in the CISA KEV catalog. The attack vector likely requires the attacker to identify a valid token ID, which may be obtained through in‑application enumeration or social engineering. The Creator role must already be present in the target base, so lateral movement or privilege escalation outside that base is not possible from this weakness alone.