Cross-Site Scripting (XSS) in graphql-playground-html (CVE-2020-4038)
Summary
Cross-site scripting in graphql-playground-html (CVE-2020-4038). Data can be tampered with by attackers. Mitigation: upgrade to 1.6.22 or later.
Original description
The description as published by the source.
GraphQL Playground (graphql-playground-html NPM package) before version 1.6.22 have a severe XSS Reflection attack vulnerability. All unsanitized user input passed into renderPlaygroundPage() method could trigger this vulnerability. This has been patched in graphql-playground-html version 1.6.22. Note that some of the associated dependent middleware packages are also affected including but not limited to graphql-playground-middleware-express before version 1.7.16, graphql-playground-middleware-koa before version 1.6.15, graphql-playground-middleware-lambda before version 1.7.17, and graphql-playground-middleware-hapi before 1.6.13.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-4038 has been found in graphql-playground-html.
Data can be tampered with by attackers.
What to do: upgrade graphql-playground-html to 1.6.22 or later.
If unsure, ask your IT team or search "graphql-playground-html CVE-2020-4038" on the vendor's site.
CVE-2020-4038 (graphql-playground-html) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.6.22 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in graphql-playground-html.
Check the vendor advisory for the affected versions of graphql-playground-html.
Severity: ?. Data can be tampered with by attackers.
Update to 1.6.22.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'graphql-playground-html' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'graphql-playground-html' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
graphql-playground-htmlを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade graphql-playground-html to 1.6.22ステージング環境で 1.6.22 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com