What is GHSA-5C7W-4WM3-85VW?

GHSA-5C7W-4WM3-85VW is a medium-severity security vulnerability in @asymmetric-effort/specifyjs (npm), affecting versions < 0.2.136. It is fixed in 0.2.136.

Which versions of @asymmetric-effort/specifyjs are affected by GHSA-5C7W-4WM3-85VW?

@asymmetric-effort/specifyjs (npm) versions < 0.2.136 is affected.

Is there a fix for GHSA-5C7W-4WM3-85VW?

Yes. GHSA-5C7W-4WM3-85VW is fixed in 0.2.136. Upgrade to this version or later.

Is GHSA-5C7W-4WM3-85VW exploitable, and should I be worried?

Whether GHSA-5C7W-4WM3-85VW 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-5C7W-4WM3-85VW 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.

GHSA-5C7W-4WM3-85VW in @asymmetric-effort/specifyjs

Q: Which versions of @asymmetric-effort/specifyjs are affected by GHSA-5C7W-4WM3-85VW?

@asymmetric-effort/specifyjs (npm) versions < 0.2.136 is affected.

Q: Is there a fix for GHSA-5C7W-4WM3-85VW?

Yes. GHSA-5C7W-4WM3-85VW is fixed in 0.2.136. Upgrade to this version or later.

Q: Is GHSA-5C7W-4WM3-85VW exploitable, and should I be worried?

Whether GHSA-5C7W-4WM3-85VW 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-5C7W-4WM3-85VW 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-5C7W-4WM3-85VW?

Upgrade @asymmetric-effort/specifyjs to 0.2.136 or later.

Summary

@asymmetric-effort/specifyjs: GraphQL gql tag allows metacharacter injection

Finding

Location: core/src/client/graphql.ts:66-80

The gql template tag function warned about interpolated values containing GraphQL metacharacters ({}():) but still concatenated them into the query string, enabling potential GraphQL injection.

Status

Fixed in v0.2.136, The gql function now throws an error when metacharacters are detected in interpolated values, forcing developers to use the variables parameter.

Impact

Affected versions

@asymmetric-effort/specifyjs (< 0.2.136)

Security releases

@asymmetric-effort/specifyjs → 0.2.136 (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

Upgrade @asymmetric-effort/specifyjs to 0.2.136 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-5C7W-4WM3-85VW? GHSA-5C7W-4WM3-85VW is a medium-severity security vulnerability in @asymmetric-effort/specifyjs (npm), affecting versions < 0.2.136. It is fixed in 0.2.136.
Which versions of @asymmetric-effort/specifyjs are affected by GHSA-5C7W-4WM3-85VW? @asymmetric-effort/specifyjs (npm) versions < 0.2.136 is affected.
Is there a fix for GHSA-5C7W-4WM3-85VW? Yes. GHSA-5C7W-4WM3-85VW is fixed in 0.2.136. Upgrade to this version or later.
Is GHSA-5C7W-4WM3-85VW exploitable, and should I be worried? Whether GHSA-5C7W-4WM3-85VW 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-5C7W-4WM3-85VW 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-5C7W-4WM3-85VW? Upgrade @asymmetric-effort/specifyjs to 0.2.136 or later.

Other vulnerabilities in @asymmetric-effort/specifyjs

CVE-IDSeverityPackage summary