Skip to main content
← All vulnerabilities
CVE-2021-41248GHSA-X4R7-M2Q9-69C8

XSS vulnerability in GraphiQL

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 1.4.7
None on Exploit-DB, Metasploit or GitHub

Summary

GraphiQL is the reference implementation of this monorepo, GraphQL IDE, an official project under the GraphQL Foundation. All versions of graphiql older than graphiql@1.4.7 are vulnerable to compromised HTTP schema introspection responses or schema prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete. In order for the attack to take place, the user must load a vulnerable schema in graphiql. There are a number of ways that can occur. By default, the schema URL is not attacker-controllable in graphiql or in its suggested implementations or examples, leaving only very complex attack vectors. If a custom implementation of graphiql's fetcher allows the schema URL to be set dynamically, such as a URL query parameter like ?endpoint= in graphql-playground, or a database provided value, then this custom graphiql implementation is vulnerable to phishing attacks, and thus much more readily available, low or no privelege level xss attacks. The URLs could look like any generic looking graphql schema URL. It should be noted that desktop clients such as Altair, Insomnia, Postwoman, do not appear to be impacted by this. This vulnerability does not impact codemirror-graphql, monaco-graphql or other dependents, as it exists in onHasCompletion.ts in graphiql. It does impact all forks of graphiql, and every released version of graphiql.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • graphql graphiql

    From 0.5.0 · fixed in 1.4.7

  • graphiqlnpm

    From 0.5.0 · fixed in 1.4.7

References 3

GitHub · graphql/graphiql

GitHub · graphql/graphql-playground