EUVD-2026-58563
GHSA-fhw4-v2hr-j5m2
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local-only vector and low-privilege access required; limited and equal C/I/A impact confined to the vulnerable system with no scope change.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
4DescriptionCVE.org
A vulnerability was identified in feedmob fm-mcp-servers 0.0.3. Affected by this vulnerability is the function downloadReport of the file src/smadex-reporting/src/index.ts of the component Download Endpoint. The manipulation of the argument downloadUrl leads to server-side request forgery. The attack can only be performed from a local environment. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.
AnalysisAI
Server-side request forgery in feedmob fm-mcp-servers 0.0.3 allows a locally authenticated attacker to manipulate the downloadUrl argument in the downloadReport function, causing the server to issue arbitrary outbound HTTP requests to attacker-controlled internal or external targets. Exploitation is constrained to local access only (AV:L), significantly limiting the practical attack surface, though a public proof-of-concept is available via GitHub issue #198. No vendor patch exists; the vendor has not responded to the coordinated disclosure.
Technical ContextAI
The affected component is the downloadReport function located in src/smadex-reporting/src/index.ts within the feedmob fm-mcp-servers package (CPE: cpe:2.3:a:feedmob:fm-mcp-servers:*:*:*:*:*:*:*:*), specifically version 0.0.3. This is a Model Context Protocol (MCP) server implementation providing integration with the Smadex advertising reporting API. The root cause is CWE-918 (Server-Side Request Forgery): the Download Endpoint accepts a downloadUrl parameter that is passed unsanitized to a server-side HTTP client, with no URL scheme restriction, allowlist enforcement, or private-IP/metadata-endpoint blocking. This allows the server to be coerced into fetching arbitrary resources from the internal network, including cloud provider metadata services or internal APIs not otherwise reachable by the attacker.
RemediationAI
No vendor-released patch has been identified at time of analysis; the vendor has not responded to the disclosure submitted via GitHub issue #198. The most effective immediate mitigation is disabling the Download Endpoint (downloadReport function) if the Smadex reporting download feature is not operationally required, which eliminates the vulnerable code path entirely. If the endpoint must remain active, restrict access so only fully trusted and audited local principals can invoke the MCP server process, reducing the PR:L attack surface. Implement network-level SSRF controls by blocking outbound requests from the server process to RFC 1918 private address ranges and cloud metadata endpoints (e.g., 169.254.169.254, fd00::/8). An application-layer URL allowlist permitting only known Smadex CDN domains in downloadUrl is the most targeted control with minimal operational side effect. Monitor the upstream repository at https://github.com/feed-mob/fm-mcp-servers for a patched release and prioritize upgrade once available.
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today