XSS vulnerability in GraphQL Playground from untrusted schemas
CVE-2021-41249GHSA-59r9-6jp6-jcm7
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (graphql-playground-react 1.7.28), redeploy, then verify what is actually installed.
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
- Affected
- < 1.7.28
- Fixed in
- 1.7.28
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-59r9-6jp6-jcm7 lists affected ranges: npm graphql-playground-react >=0 <1.7.28 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-59r9-6jp6-jcm7 lists affected ranges: npm graphql-playground-react >=0 <1.7.28
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L
- EPSS
- CVE-2021-41249: 1.22% estimated exploitation activity in the next 30 days; percentile 68.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
GraphQL Playground introspection schema template injection attack: Advisory Statement This is a security advisory for an XSS vulnerability in graphql-playground. A similar vulnerability affects graphiql, the package from which graphql-playground was forked. There is a corresponding graphiql advisory. - 1. Impact - 2. Scope - 3. Patches - 4. Reproducing the exploit - 5. Credit - 6. For more information 1. Impact All versions of graphql-playground-react older than graphql-playground-react@1.7.28 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 malicious schema in graphql-playground. There are several ways this can occur, including by specifying the URL to a malicious schema in the endpoint query parameter. If a user clicks on a link to a GraphQL Playground…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-59r9-6jp6-jcm7
- Revision 1 · created ·
Published from osv record GHSA-59r9-6jp6-jcm7
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2021-41249 Advisory: XSS vulnerability in GraphQL Playground from untrusted schemas IDs: CVE-2021-41249, GHSA-59r9-6jp6-jcm7 Record: https://patchnext.com/advisories/cve-2021-41249 (revision 2, source checked 26 Oct 2026, 12:21 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: graphql-playground-react 1.7.28. A vendor fix does not mean a deployment is fixed. ## Affected components - npm graphql-playground-react: affected < 1.7.28; fixed in 1.7.28 ## Suggested inspection (read-only) - `npm ls graphql-playground-react --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on graphql-playground-react. - 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://osv.dev/vulnerability/GHSA-59r9-6jp6-jcm7 (OSV record GHSA-59r9-6jp6-jcm7 lists affected ranges: npm graphql-playground-react >=0 <1.7.28 (fixed)) - Verified: https://github.com/advisories/GHSA-59r9-6jp6-jcm7 (GitHub-reviewed advisory GHSA-59r9-6jp6-jcm7 lists affected ranges: npm graphql-playground-react >=0 <1.7.28) Commands are suggestions: review each one before running it.
Loading voting…