What is GHSA-V3F4-W7R7-V3HM?

GHSA-V3F4-W7R7-V3HM is a high-severity cross-site request forgery (CSRF) vulnerability in @zenalexa/unicli (npm), affecting versions < 0.225.2. It is fixed in 0.225.2. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.

Which versions of @zenalexa/unicli are affected by GHSA-V3F4-W7R7-V3HM?

@zenalexa/unicli (npm) versions < 0.225.2 is affected.

Is there a fix for GHSA-V3F4-W7R7-V3HM?

Yes. GHSA-V3F4-W7R7-V3HM is fixed in 0.225.2. Upgrade to this version or later.

Is GHSA-V3F4-W7R7-V3HM exploitable, and should I be worried?

Whether GHSA-V3F4-W7R7-V3HM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-V3F4-W7R7-V3HM is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-V3F4-W7R7-V3HM?

Upgrade @zenalexa/unicli to 0.225.2 or later.

GHSA-V3F4-W7R7-V3HM in @zenalexa/unicli

Q: Which versions of @zenalexa/unicli are affected by GHSA-V3F4-W7R7-V3HM?

@zenalexa/unicli (npm) versions < 0.225.2 is affected.

Q: Is there a fix for GHSA-V3F4-W7R7-V3HM?

Yes. GHSA-V3F4-W7R7-V3HM is fixed in 0.225.2. Upgrade to this version or later.

Q: Is GHSA-V3F4-W7R7-V3HM exploitable, and should I be worried?

Whether GHSA-V3F4-W7R7-V3HM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-V3F4-W7R7-V3HM is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-V3F4-W7R7-V3HM?

Upgrade @zenalexa/unicli to 0.225.2 or later.

Summary

Uni-CLI: Legacy HTTP MCP transport accepted browser-originated localhost requests

Workarounds

Upgrade to 0.225.2 or later. If upgrading is not immediately possible, do not expose the legacy HTTP MCP transport to browser-originated traffic; use the default stdio transport or the Streamable HTTP transport instead.

Credits

Reported privately by Ryan Vonbrubeck (@dodge1218).

Impact

Uni-CLI versions before 0.225.2 exposed the legacy JSON-RPC-over-HTTP MCP transport on loopback without validating browser Origin headers before routing requests. A malicious web page could send a CORS simple POST request, such as text/plain, to the local /mcp endpoint and deliver a JSON-RPC body to the dispatcher. If the user had started the local MCP HTTP transport, that page could drive tools/call requests against the user's local Uni-CLI server.

The Streamable HTTP transport already enforced this browser-to-localhost boundary. The legacy stateless HTTP path did not, so the two HTTP transports had drifted. This issue is about the browser-to-localhost boundary; it does not change Uni-CLI's local-code-execution trust model.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

Affected versions

@zenalexa/unicli (< 0.225.2)

Security releases

@zenalexa/unicli → 0.225.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Version 0.225.2 fixes the issue by moving the Origin policy into a shared guard and applying it before routing in both HTTP transports. Non-loopback browser Origins are rejected with HTTP 403 before health, OAuth, or /mcp dispatch runs. Non-browser clients that omit Origin remain supported.

Frequently Asked Questions

What is GHSA-V3F4-W7R7-V3HM? GHSA-V3F4-W7R7-V3HM is a high-severity cross-site request forgery (CSRF) vulnerability in @zenalexa/unicli (npm), affecting versions < 0.225.2. It is fixed in 0.225.2. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
Which versions of @zenalexa/unicli are affected by GHSA-V3F4-W7R7-V3HM? @zenalexa/unicli (npm) versions < 0.225.2 is affected.
Is there a fix for GHSA-V3F4-W7R7-V3HM? Yes. GHSA-V3F4-W7R7-V3HM is fixed in 0.225.2. Upgrade to this version or later.
Is GHSA-V3F4-W7R7-V3HM exploitable, and should I be worried? Whether GHSA-V3F4-W7R7-V3HM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-V3F4-W7R7-V3HM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-V3F4-W7R7-V3HM? Upgrade @zenalexa/unicli to 0.225.2 or later.