Skip to content

← Public intelligence

npm package

docusaurus-plugin-content-gists

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 10.0npmAmendedPublished

    docusaurus-plugin-content-gists vulnerability exposes GitHub Personal Access Token

    CVE-2025-53624 · GHSA-qf34-qpr4-5pph

    Affected
    • npm docusaurus-plugin-content-gists < 4.0.0
    Fixed in
    4.0.0· Vendor fix available
    Issue
    GitHub Personal Access Token Exposure in docusaurus-plugin-content-gists Summary 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. Affected Versions - All versions < 4.0.0 Patched Versions - Version 4.0.0 and later Impact When using the affected versions with the recommended configuration pattern: The GitHub Personal Access Token is included in the webpack bundle and exposed in production builds at: - /build/assets/js/main.[hash].js This allows malicious actors to: - Extract the GitHub Personal Access Token from the website's JavaScript files - Use the stolen token to access the token owner's GitHub account with the granted permissions - Potentially access…

    Recommended action: Upgrade to 4.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →