Pipeboard-co meta-ads-mcp
Meta Ads MCP: X-Pipeboard-Token Header Auth Bypass Reuses Operator Meta Token
Meta Ads MCP is a Model Context Protocol (MCP) server that lets AI assistants run Meta Ads. Prior to version 1.0.115, AuthInjectionMiddleware in meta_ads_mcp/core/http_auth_integration.py rejects HTTP MCP requests only when both auth_token and pipeboard_token are absent, while extract_token_from_headers() does not recognize X-Pipeboard-Token as a primary credential. A network caller using the streamable-http transport can therefore send any X-Pipeboard-Token value, pass the guard without establishing authentication context, and cause get_auth_token() to fall back to the server operator's META_ACCESS_TOKEN. Subsequent MCP tools execute with the operator's Meta credentials and can read or modify the operator's Meta Ads data. Deployments using the default stdio transport or without META_ACCESS_TOKEN are not affected. This issue is fixed in version 1.0.115.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.0.115
Fixed in 1.0.115
Mitigation
Upgrade meta-ads-mcp to 1.0.115 or later.
References
- Vendor advisory github.com/pipeboard-co/meta-ads-mcp/security/…
- Patch github.com/pipeboard-co/meta-ads-mcp/pull/137
- Patch github.com/pipeboard-co/meta-ads-mcp/commit/95…
1 more
- Release notes github.com/pipeboard-co/meta-ads-mcp/releases/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.