Description

A security vulnerability has been detected in adafap api-mcp up to 92b9a5d04acfec165c7d4ef852496593aa87be06. This affects the function customAxios of the file app/api/proxy/route.ts of the component Proxy API Endpoint. The manipulation of the argument url leads to server-side request forgery. The attack is possible to be carried out remotely. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.3",
  "pubDate": "2026-08-09T23:16:36.487Z",
  "pubdate": "2026-08-09T23:16:36.487Z",
  "executiveSummary": "A Server-Side Request Forgery (SSRF) vulnerability has been identified in the adafap api-mcp component up to commit 92b9a5d04acfec165c7d4ef852496593aa87be06. The vulnerability resides in the customAxios function within the app/api/proxy/route.ts file. This security flaw allows remote attackers to manipulate the url argument, forcing the server to dispatch arbitrary outbound HTTP requests to unintended destinations. The impact of this vulnerability includes potential unauthorized access to internal network resources, sensitive metadata services, or private endpoints that are otherwise shielded from the public internet. The product utilizes a rolling release model, meaning specific fixed version numbers are unavailable. Exploitation can be executed remotely without requiring prior authentication or privileged access, presenting a significant risk to deployments exposed to untrusted networks. The project has been notified via an issue report but has not yet provided a response or official patch.",
  "technicalDetails": "The vulnerability is caused by insufficient input validation and lack of proper sanitization on user-supplied URL parameters within the Proxy API Endpoint component. Specifically, the customAxios function located in app/api/proxy/route.ts processes the url argument directly to initiate outbound requests using the underlying HTTP client library without enforcing strict allowlists, protocol restrictions, or IP address filtering.\nThe attack flow begins when a remote, unauthenticated attacker sends a crafted HTTP request to the vulnerable proxy endpoint, supplying an arbitrary or internal URI within the vulnerable url parameter. Upon receiving the input, the customAxios function fails to validate whether the target destination resolves to a safe external domain or an internal network resource (such as localhost, RFC 1918 private IP spaces, or cloud provider metadata endpoints).\nConsequently, the server executes the request on behalf of the attacker, relaying the response back or potentially acting as a pivot point for further internal network reconnaissance. Because the application exposes this proxy functionality over the network, attackers can leverage the server's network positioning to interact with backend services, internal APIs, and databases that lack adequate perimeter defenses. Post-exploitation impact heavily depends on the internal network architecture, potentially leading to data exfiltration, service enumeration, or remote code execution if internal endpoints contain unauthenticated administrative functions."
}