dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-53624

CRITICAL · 10.0 CVSS v3.1 Published 2025-07-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Docusaurus gists plugin adds a page to your Docusaurus instance, displaying all public gists of a GitHub user. docusaurus-plugin-content-gists versions prior to 4.0.0 are vulnerable to exposing GitHub Personal Access Tokens in production build artifacts when passed through plugin configuration options. The token, intended for build-time API access only, is inadvertently included in client-side JavaScript bundles, making it accessible to anyone who can view the website's source code. This vulnerability is fixed in 4.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The docusaurus-plugin-content-gists plugin versions before 4.0.0 improperly include GitHub Personal Access Tokens configured for build-time API access directly into client-side JavaScript bundles. Anyone viewing the website source can extract these tokens, granting them access to the associated GitHub account.

MitigationUpgrade docusaurus-plugin-content-gists to version 4.0.0 or later. Immediately rotate any PATs that may have been exposed in production builds prior to the upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if docusaurus-plugin-content-gists is in use
    Check package.json for 'docusaurus-plugin-content-gists' in dependencies or list installed npm packages with npm list docusaurus-plugin-content-gists
    Affected if The plugin is listed as a dependency
  2. Check the installed plugin version
    Run 'npm list docusaurus-plugin-content-gists' or inspect the version in package.json and compare to the affected range (versions before 4.0.0)
    Affected if Version is below 4.0.0
  3. Verify if GitHub PAT is configured for the plugin
    Inspect docusaurus.config.js or the plugin configuration file for 'gists' or 'githubToken' settings under the docusaurus-plugin-content-gists configuration
    Affected if A GitHub Personal Access Token is configured for the plugin
  4. Check for production builds that may have exposed tokens
    Look for built JavaScript files in the 'build' or 'dist' directory, or inspect any archived production builds
    Affected if Production builds exist from when the vulnerable plugin version was in use
  5. Inspect built JS bundles for token exposure
    Search the built JavaScript files (in build/static/js) for the configured GitHub token string using grep or a text search
    Affected if The token string or patterns resembling it appear in any client-side JavaScript files

Users are affected if docusaurus-plugin-content-gists version is below 4.0.0, a GitHub PAT was configured, and production builds were generated, resulting in token exposure in client-side bundles.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade docusaurus-plugin-content-gists to version 4.0.0 or later. Immediately rotate any PATs that may have been exposed in production builds prior to the upgrade.

Recommended fix High confidence

4.0.0

  1. Check the current version of docusaurus-plugin-content-gists in your package.json file
  2. Update the package version to 4.0.0 (or latest available version if higher) in package.json
  3. Run 'npm install' or 'yarn install' to install the updated package
  4. Rebuild your Docusaurus application with the updated package
  5. Verify that GitHub Personal Access Tokens are no longer exposed in the generated JavaScript bundles by inspecting the build output
Caveat No breaking changes documented in the CVE description

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53624 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data