CVE-2026-54547: CWE-287: Improper Authentication in pipeboard-co meta-ads-mcp
CVE-2026-54547 is an improper authentication vulnerability in pipeboard-co's meta-ads-mcp server prior to version 1.0.115. The issue arises because the AuthInjectionMiddleware only rejects requests when both auth_token and pipeboard_token are absent, but the token extraction does not treat X-Pipeboard-Token as a primary credential. This allows an attacker using the streamable-http transport to bypass authentication and cause the server to use the operator's META_ACCESS_TOKEN, enabling unauthorized access to Meta Ads data. Deployments using the default stdio transport or without META_ACCESS_TOKEN are not affected. The vulnerability is fixed in version 1.0.115.
AI Analysis
Technical Summary
Meta Ads MCP is a server component that enables AI assistants to run Meta Ads. Before version 1.0.115, the authentication middleware (AuthInjectionMiddleware) only rejects HTTP MCP requests if both auth_token and pipeboard_token are missing. However, the function extract_token_from_headers() does not recognize the X-Pipeboard-Token header as a primary credential. Consequently, an attacker sending any X-Pipeboard-Token value over the streamable-http transport can bypass authentication checks. This causes get_auth_token() to fall back to the server operator's META_ACCESS_TOKEN, granting the attacker the operator's Meta credentials. This allows unauthorized reading or modification of the operator's Meta Ads data. The issue is resolved in version 1.0.115.
Potential Impact
An attacker can bypass authentication when using the streamable-http transport and gain access to the server operator's Meta credentials (META_ACCESS_TOKEN). This enables unauthorized reading and modification of Meta Ads data associated with the operator. Deployments that use the default stdio transport or do not have META_ACCESS_TOKEN configured are not affected.
Mitigation Recommendations
Upgrade meta-ads-mcp to version 1.0.115 or later, where this authentication bypass vulnerability is fixed. If upgrading is not immediately possible, avoid using the streamable-http transport or ensure META_ACCESS_TOKEN is not configured to prevent exploitation.
CVE-2026-54547: CWE-287: Improper Authentication in pipeboard-co meta-ads-mcp
Description
CVE-2026-54547 is an improper authentication vulnerability in pipeboard-co's meta-ads-mcp server prior to version 1.0.115. The issue arises because the AuthInjectionMiddleware only rejects requests when both auth_token and pipeboard_token are absent, but the token extraction does not treat X-Pipeboard-Token as a primary credential. This allows an attacker using the streamable-http transport to bypass authentication and cause the server to use the operator's META_ACCESS_TOKEN, enabling unauthorized access to Meta Ads data. Deployments using the default stdio transport or without META_ACCESS_TOKEN are not affected. The vulnerability is fixed in version 1.0.115.
CVSS v3.1
Score 7.4high
Affected software
pipeboard-co
meta-ads-mcp
pkg:github/pipeboard-co/meta-ads-mcpRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Meta Ads MCP is a server component that enables AI assistants to run Meta Ads. Before version 1.0.115, the authentication middleware (AuthInjectionMiddleware) only rejects HTTP MCP requests if both auth_token and pipeboard_token are missing. However, the function extract_token_from_headers() does not recognize the X-Pipeboard-Token header as a primary credential. Consequently, an attacker sending any X-Pipeboard-Token value over the streamable-http transport can bypass authentication checks. This causes get_auth_token() to fall back to the server operator's META_ACCESS_TOKEN, granting the attacker the operator's Meta credentials. This allows unauthorized reading or modification of the operator's Meta Ads data. The issue is resolved in version 1.0.115.
Potential Impact
An attacker can bypass authentication when using the streamable-http transport and gain access to the server operator's Meta credentials (META_ACCESS_TOKEN). This enables unauthorized reading and modification of Meta Ads data associated with the operator. Deployments that use the default stdio transport or do not have META_ACCESS_TOKEN configured are not affected.
Mitigation Recommendations
Upgrade meta-ads-mcp to version 1.0.115 or later, where this authentication bypass vulnerability is fixed. If upgrading is not immediately possible, avoid using the streamable-http transport or ensure META_ACCESS_TOKEN is not configured to prevent exploitation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-15T19:04:14.456Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa9812f55bf5e2cf527c2d1
Added to database: 09/15/2026, 17:32:31 UTC
Last enriched: 09/15/2026, 17:46:38 UTC
Last updated: 09/15/2026, 18:29:49 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.