@profullstack/mcp-server vulnerable to OS Command Injection in domain_lookup Module
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @profullstack/mcp-server
- Affected
- <= 1.4.12
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-v6wj-c83f-v46x lists affected ranges: npm @profullstack/mcp-server >=0 <=1.4.12
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-v6wj-c83f-v46x lists affected ranges: npm @profullstack/mcp-server >=0 <=1.4.12
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
<html <body <!--StartFragment--<html<head</head<body<h1Security Advisory: OS Command Injection in <codeprofullstack/mcp-server</code <codedomainlookup</code Module</h1 Field | Value -- | -- Project | profullstack/mcp-server Repository | https://github.com/profullstack/mcp-server Affected Commit | 2e8ea913573610667ad54e31dba2e8198ebf7cf9 Affected Module | mcpmodules/domainlookup Affected Endpoints | POST /domain-lookup/check, POST /domain-lookup/bulk Vulnerability Type | CWE-78: OS Command Injection CVSS 3.1 Score | 9.8 (Critical) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Authentication Required | None Default Network Exposure | Bind address 0.0.0.0, no global authentication middleware Validated | 2026-04-21 (initial), 2026-04-28 (re-confirmed) <hr <h2Summary</h2 <pThe <codedomainlookup</code module assembles a shell command string by concatenating user-controlled input (<codedomains</code / <codekeywords</code) and passes it to <codeexecAsync()</code. Both HTTP endpoints reach the same…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-v6wj-c83f-v46x
- Revision 2 · amended ·
Amended from osv record GHSA-v6wj-c83f-v46x
- Revision 1 · created ·
Published from ghsa record GHSA-v6wj-c83f-v46x
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-v6wj-c83f-v46x Advisory: @profullstack/mcp-server vulnerable to OS Command Injection in domain_lookup Module IDs: GHSA-v6wj-c83f-v46x Record: https://patchnext.com/advisories/ghsa-v6wj-c83f-v46x (revision 3, source checked 26 Oct 2026, 12:51 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @profullstack/mcp-server: affected <= 1.4.12 ## Suggested inspection (read-only) - `npm ls @profullstack/mcp-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @profullstack/mcp-server. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-v6wj-c83f-v46x (GitHub-reviewed advisory GHSA-v6wj-c83f-v46x lists affected ranges: npm @profullstack/mcp-server >=0 <=1.4.12) - Verified: https://osv.dev/vulnerability/GHSA-v6wj-c83f-v46x (OSV record GHSA-v6wj-c83f-v46x lists affected ranges: npm @profullstack/mcp-server >=0 <=1.4.12) Commands are suggestions: review each one before running it.
Loading voting…