CVE-2025-53624: Docusaurus plugin content gists Docusaurus-plugin-content-gists Vulnerability Exposes GitHub Personal Vulnerability

CRITICAL
Advisory Identifier: GHSA-qf34-qpr4-5pph
CVSS 10.0
CWE-200
Published
Advisory Summary

CVE-2025-53624 is a CRITICAL (CVSS 10.0) docusaurus-plugin-content-gists vulnerability exposes github personal vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Docusaurus plugin content gists libraries in the npm ecosystem. The issue involves docusaurus-plugin-content-gists vulnerability exposes github personal access token. Remediation is available by upgrading affected packages to version 4.0.0.

CVE-2025-53624 at a Glance

CVE Identifier CVE-2025-53624
GHSA Identifier GHSA-qf34-qpr4-5pph
Severity CRITICAL
CVSS v3.1 Base Score 10.0
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Docusaurus plugin content gists
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 10.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2025-53624

To remediate this vulnerability, upgrade all affected Docusaurus plugin content gists dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

docusaurus-plugin-content-gists fixed: 4.0.0
npm install docusaurus-plugin-content-gists@4.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls docusaurus-plugin-content-gists

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-53624, inspect your project dependencies using npm:

npm ls docusaurus-plugin-content-gists

Analyze the terminal output to locate any version of Docusaurus plugin content gists in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.0.0), your application is affected.

Note: The npm ls docusaurus-plugin-content-gists command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Docusaurus plugin content gists, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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: ```javascript plugins: [ [ 'docusaurus-plugin-content-gists', { personalAccessToken: process.env.GITHUB_PERSONAL_ACCESS_TOKEN, }, ], ] ``` 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 private gists, repositories, or perform other actions depending on the token's scope ## Mitigation steps 1. Immediately revoke access to the GitHub PAT that was used: https://github.com/settings/tokens ### Migration steps 1. Update to version 4.0.0+: `npm install docusaurus-plugin-content-gists@^4.0.0` 3. Remove `personalAccessToken` from your plugin configuration 4. Ensure `GH_PERSONAL_ACCESS_TOKEN` is set in your build environment

CVE-2025-53624 Affected Docusaurus plugin content gists Versions

1 component(s)
Fixed Versions:
4.0.0
Product / Package Ecosystem Affected Versions Fixed Version
docusaurus-plugin-content-gists
npm
< 4.0.0
4.0.0

References

Frequently Asked Questions

What is CVE-2025-53624?
CVE-2025-53624 is a security vulnerability in Docusaurus plugin content gists involving docusaurus-plugin-content-gists vulnerability exposes GitHub Personal Access Token under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Docusaurus plugin content gists versions are affected?
Affected versions include releases prior to 4.0.0 across affected packages: docusaurus-plugin-content-gists.
What version fixes CVE-2025-53624?
Upgrading to 4.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is docusaurus-plugin-content-gists affected?
Yes, docusaurus-plugin-content-gists is affected in releases prior to 4.0.0. Upgrade your dependency to 4.0.0 or later.
What is the CVSS score of CVE-2025-53624?
CVE-2025-53624 has a CVSS v3.1 base score of 10.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2025-53624?
CVE-2025-53624 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check npm dependencies for CVE-2025-53624?
Run the dependency tree command: 'npm ls docusaurus-plugin-content-gists'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qf34-qpr4-5pph",
  "modified" : "2025-07-09T22:40:07Z",
  "published" : "2025-07-09T22:40:06Z",
  "aliases" : [ "CVE-2025-53624" ],
  "summary" : "docusaurus-plugin-content-gists vulnerability exposes GitHub Personal Access Token",
  "details" : "## GitHub Personal Access Token Exposure in docusaurus-plugin-content-gists\n\n### Summary\n\ndocusaurus-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.\n\n### Affected Versions\n\n- All versions < 4.0.0\n\n### Patched Versions\n\n- Version 4.0.0 and later\n\n### Impact\n\nWhen using the affected versions with the recommended configuration pattern:\n\n```javascript\nplugins: [\n  [\n    'docusaurus-plugin-content-gists',\n    {\n      personalAccessToken: process.env.GITHUB_PERSONAL_ACCESS_TOKEN,\n    },\n  ],\n]\n```\n\nThe GitHub Personal Access Token is included in the webpack bundle and exposed in production builds at:\n- `/build/assets/js/main.[hash].js`\n\nThis allows malicious actors to:\n- Extract the GitHub Personal Access Token from the website's JavaScript files\n- Use the stolen token to access the token owner's GitHub account with the granted permissions\n- Potentially access private gists, repositories, or perform other actions depending on the token's scope\n\n## Mitigation steps\n\n  1. Immediately revoke access to the GitHub PAT that was used: https://github.com/settings/tokens\n\n### Migration steps\n\n  1. Update to version 4.0.0+: `npm install docusaurus-plugin-content-gists@^4.0.0`\n  3. Remove `personalAccessToken` from your plugin configuration\n  4. Ensure `GH_PERSONAL_ACCESS_TOKEN` is set in your build environment",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "docusaurus-plugin-content-gists"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/webbertakken/docusaurus-plugin-content-gists/security/advisories/GHSA-qf34-qpr4-5pph"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-53624"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/webbertakken/docusaurus-plugin-content-gists/commit/8d4230b82412edb215ddfa9e609d178510a5fe31"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/webbertakken/docusaurus-plugin-content-gists"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-07-09T22:40:06Z",
    "nvd_published_at" : "2025-07-09T21:15:27Z"
  }
}