Airtable MCP CLI before 0.2.5 Credential Disclosure via Unvalidated Configured Endpoint
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Airtable | airtable-mcp-cli | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Airtable | Airtable-mcp-cli |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.446% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Airtable
Airtable airtable-mcp-cli |
|
| Vendors & Products |
Airtable
Airtable airtable-mcp-cli |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The configure command accepted any endpoint URL and stored it beside the user's access token. ConfigureCommand.execute in src/cli.ts persisted the value given to its endpoint option into the user profile without passing it through createSafeUrl in src/config.ts, the helper that already restricted the environment-variable form of the same setting to the vendor's own hosts over HTTPS. Because the connect path in src/mcp.ts attaches the stored token as a bearer credential on every request to the configured endpoint, a user who was persuaded to run configure with an endpoint of the attacker's choosing sent their personal access token to that destination on each subsequent invocation. Version 0.2.5 applies the same helper to the option. | |
| Title | Airtable MCP CLI before 0.2.5 Credential Disclosure via Unvalidated Configured Endpoint | |
| Weaknesses | CWE-200 | |
| References |
| |
| Metrics |
cvssV3_1
|