Information Disclosure in gatsby-source-wordpress (CVE-2021-32770)
Summary
Vulnerability in gatsby-source-wordpress (CVE-2021-32770). Confidential information can be exposed externally. Mitigation: upgrade to 5.9.2 or later.
Original description
The description as published by the source.
Impact
The gatsby-source-wordpress plugin prior to versions 4.0.8 and 5.9.2 leaks .htaccess HTTP Basic Authentication variables into the app.js bundle during build-time. Users who are not initializing basic authentication credentials in the gatsby-config.js are not affected.
Example affected gatsby-config.js:
resolve: 'gatsby-source-wordpress',
auth: {
htaccess: {
username: leaked_username
password: leaked_password,
},
},
Patches
A patch has been introduced in gatsby-source-wordpress@4.0.8 and gatsby-source-wordpress@5.9.2 which mitigates the issue by filtering all variables specified in the auth: { } section. Users that depend on this functionality are advised to upgrade to the latest release of gatsby-source-wordpress, run gatsby clean followed by a gatsby build.
Workarounds
There is no known workaround at this time, other than manually editing the app.js file post-build.
For more information
Email us at security@gatsbyjs.com
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-2021-32770 has been found in gatsby-source-wordpress.
Confidential information can be exposed externally.
What to do: upgrade gatsby-source-wordpress to 5.9.2 or later.
If unsure, ask your IT team or search "gatsby-source-wordpress CVE-2021-32770" on the vendor's site.
CVE-2021-32770 (gatsby-source-wordpress) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.9.2 — 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.
Information disclosure (CWE-200) exists in gatsby-source-wordpress.
Check the vendor advisory for the affected versions of gatsby-source-wordpress.
Severity: ?. Confidential information can be exposed externally.
Update to 5.9.2.
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 'gatsby-source-wordpress' . 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 'gatsby-source-wordpress' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gatsby-source-wordpressを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gatsby-source-wordpress to 5.9.2ステージング環境で 5.9.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com