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

published 2026-07-02 4mo ago modified 2026-09-10 2mo ago

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

## 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.

Patch / fix

fixed in 1 links 1

npm @asymmetric-effort/specifyjs 0.2.136

github.com/asymmetric-effort/specifyjs@25d1fb4 commit

Is GHSA-5c7w-4wm3-85vw in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
npm	@asymmetric-effort/specifyjs	<0.2.136	0.2.136

Classification

Weakness

CWE-943 Improper Neutralization of Special Elements in Data Query Logic

References

Sources

GitHub Advisory GHSA-5c7w-4wm3-85vw

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.