Homepage

meta-ads-mcp@1.0.100

Model Context Protocol (MCP) server for Meta Ads - Use Remote MCP at pipeboard.co for easiest setup

  • latest version

    1.0.120

  • latest non vulnerable version

    1.0.120

  • first published

    1 years ago

  • latest version published

    10 days ago

  • licenses detected

  • View meta-ads-mcp package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the meta-ads-mcp package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Server-side Request Forgery (SSRF)

    meta-ads-mcp is a Model Context Protocol (MCP) server for Meta Ads - Use Remote MCP at pipeboard.co for easiest setup

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the upload_ad_image process. An attacker can cause the server to make arbitrary outbound HTTP requests to internal or external endpoints by supplying a crafted image_url parameter. This is only exploitable if the server is deployed with the streamable-http transport mode and the attacker can send requests to the MCP HTTP endpoint with any non-empty Bearer token.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade meta-ads-mcp to version 1.0.115 or higher.

    [,1.0.115)
    • C
    Insufficiently Protected Credentials

    meta-ads-mcp is a Model Context Protocol (MCP) server for Meta Ads - Use Remote MCP at pipeboard.co for easiest setup

    Affected versions of this package are vulnerable to Insufficiently Protected Credentials via the AuthInjectionMiddleware.dispatch process. An attacker can gain unauthorized access to operator credentials and invoke privileged actions by sending unauthenticated HTTP requests to the MCP server, which are processed without authentication checks. This results in the operator's access token being exposed in the response payload when a downstream API error occurs.

    How to fix Insufficiently Protected Credentials?

    Upgrade meta-ads-mcp to version 1.0.109 or higher.

    [,1.0.109)
    Go back to all versions of this package