A Leader in the 2026 Gartner® Magic Quadrant™ for Endpoint Protection. Six years running.Six years. Gartner® Magic Quadrant™ Leader.Find Out Why
Experiencing a Breach?Blog
Get StartedContact Us
SentinelOne
  • Platform
    Platform Overview
    • Singularity Platform
      Welcome to Integrated Enterprise Security
    • AI for Security
      Leading the Way in AI-Powered Security Solutions
    • Securing AI
      Accelerate AI Adoption with Secure AI Tools, Apps, and Agents.
    • How It Works
      The Singularity XDR Difference
    • Singularity Marketplace
      One-Click Integrations to Unlock the Power of XDR
    • Pricing & Packaging
      Comparisons and Guidance at a Glance
    Data & AI
    • Purple AI
      Accelerate SecOps with Generative AI
    • Singularity Hyperautomation
      Easily Automate Security Processes
    • AI-SIEM
      The AI SIEM for the Autonomous SOC
    • AI Data Pipelines
      Security Data Pipeline for AI SIEM and Data Optimization
    • Singularity Data Lake
      AI-Powered, Unified Data Lake
    • Singularity Data Lake for Log Analytics
      Seamlessly Ingest Data from On-Prem, Cloud or Hybrid Environments
    Endpoint Security
    • Singularity Endpoint
      Autonomous Prevention, Detection, and Response
    • Singularity XDR
      Native & Open Protection, Detection, and Response
    • Singularity RemoteOps Forensics
      Orchestrate Forensics at Scale
    • Singularity Threat Intelligence
      Comprehensive Adversary Intelligence
    • Singularity Vulnerability Management
      Application & OS Vulnerability Management
    • Singularity Identity
      Identity Threat Detection and Response
    Cloud Security
    • Singularity Cloud Security
      Block Attacks with an AI-Powered CNAPP
    • Singularity Cloud Native Security
      Secure Cloud and Development Resources
    • Singularity Cloud Workload Security
      Real-Time Cloud Workload Protection Platform
    • Singularity Cloud Data Security
      AI-Powered Threat Detection for Cloud Storage
    • Singularity Cloud Security Posture Management
      Detect and Remediate Cloud Misconfigurations
    Securing AI
    • Prompt Security
      Secure AI Tools Across Your Enterprise
  • Why SentinelOne?
    Why SentinelOne?
    • Why SentinelOne?
      Cybersecurity Built for What’s Next
    • Our Customers
      Trusted by the World’s Leading Enterprises
    • Industry Recognition
      Tested and Proven by the Experts
    • About Us
      The Industry Leader in Autonomous Cybersecurity
    Compare SentinelOne
    • Arctic Wolf
    • Broadcom
    • CrowdStrike
    • Cybereason
    • Microsoft
    • Palo Alto Networks
    • Sophos
    • Splunk
    • Trellix
    • Trend Micro
    • Wiz
    Verticals
    • Energy
    • Federal Government
    • Finance
    • Healthcare
    • Higher Education
    • K-12 Education
    • Manufacturing
    • Retail
    • State and Local Government
  • Services
    Managed Services
    • Managed Services Overview
      Wayfinder Threat Detection & Response
    • Threat Hunting
      World-Class Expertise and Threat Intelligence
    • Managed Detection & Response
      24/7/365 Expert MDR Across Your Entire Environment
    • Incident Readiness & Response
      DFIR, Breach Readiness, & Compromise Assessments
    Support, Deployment, & Health
    • Technical Account Management
      Customer Success with Personalized Service
    • SentinelOne GO
      Guided Onboarding & Deployment Advisory
    • SentinelOne University
      Live and On-Demand Training
    • Services Overview
      Comprehensive Solutions for Seamless Security Operations
    • SentinelOne Community
      Community Login
  • Partners
    Our Network
    • MSSP Partners
      Succeed Faster with SentinelOne
    • Singularity Marketplace
      Extend the Power of S1 Technology
    • Cyber Risk Partners
      Enlist Pro Response and Advisory Teams
    • Technology Alliances
      Integrated, Enterprise-Scale Solutions
    • SentinelOne for AWS
      Hosted in AWS Regions Around the World
    • Channel Partners
      Deliver the Right Solutions, Together
    • SentinelOne for Google Cloud
      Unified, Autonomous Security Giving Defenders the Advantage at Global Scale
    • Partner Locator
      Your Go-to Source for Our Top Partners in Your Region
    Partner Portal→
  • Resources
    Resource Center
    • Case Studies
    • Data Sheets
    • eBooks
    • Reports
    • Videos
    • Webinars
    • Whitepapers
    • Events
    View All Resources→
    Blog
    • Feature Spotlight
    • For CISO/CIO
    • From the Front Lines
    • Identity
    • Cloud
    • macOS
    • SentinelOne Blog
    Blog→
    Tech Resources
    • SentinelLABS
    • Ransomware Anthology
    • Cybersecurity 101
  • About
    About SentinelOne
    • About SentinelOne
      The Industry Leader in Cybersecurity
    • Investor Relations
      Financial Information & Events
    • SentinelLABS
      Threat Research for the Modern Threat Hunter
    • Careers
      The Latest Job Opportunities
    • Press & News
      Company Announcements
    • Cybersecurity Blog
      The Latest Cybersecurity Threats, News, & More
    • FAQ
      Get Answers to Our Most Frequently Asked Questions
    • DataSet
      The Live Data Platform
    • S Foundation
      Securing a Safer Future for All
    • S Ventures
      Investing in the Next Generation of Security, Data and AI
  • Pricing
Get StartedContact Us
CVE Vulnerability Database
Vulnerability Database/CVE-2025-53624

CVE-2025-53624: Docusaurus Gists Plugin Token Exposure

CVE-2025-53624 is a token exposure flaw in docusaurus-plugin-content-gists that leaks GitHub Personal Access Tokens in production builds. This article covers the technical details, affected versions, and mitigation steps.

Published: March 18, 2026

CVE-2025-53624 Overview

CVE-2025-53624 is a critical information disclosure vulnerability affecting the Docusaurus gists plugin (docusaurus-plugin-content-gists). The plugin, designed to display all public gists of a GitHub user on a Docusaurus instance, inadvertently exposes GitHub Personal Access Tokens (PATs) in production build artifacts when tokens are passed through plugin configuration options. This sensitive credential, intended solely for build-time API access, becomes embedded in client-side JavaScript bundles and is accessible to anyone who can view the website's source code.

Critical Impact

GitHub Personal Access Tokens leaked in client-side JavaScript bundles can be harvested by attackers to gain unauthorized access to GitHub repositories, potentially leading to source code theft, malicious code injection, or complete account compromise depending on the token's permissions scope.

Affected Products

  • docusaurus-plugin-content-gists versions prior to 4.0.0
  • Docusaurus instances using the vulnerable plugin with PAT configuration
  • Any website built with the affected plugin versions where PAT was passed via plugin options

Discovery Timeline

  • 2025-07-09 - CVE CVE-2025-53624 published to NVD
  • 2025-07-10 - Last updated in NVD database

Technical Details for CVE-2025-53624

Vulnerability Analysis

This vulnerability stems from improper handling of sensitive configuration data during the Docusaurus build process. The plugin architecture failed to properly separate build-time credentials from runtime client-side code, resulting in the GitHub Personal Access Token being bundled directly into the JavaScript assets served to browsers.

When Docusaurus builds a site, plugin configurations are processed and can inadvertently be serialized into the client-side bundle if not properly filtered. In vulnerable versions, the entire configuration object—including the PAT—was accessible in the browser's JavaScript context, making token extraction trivial for any visitor inspecting the page source or network requests.

The vulnerability is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), reflecting the core issue of credential leakage to untrusted parties.

Root Cause

The root cause lies in the plugin's failure to implement proper separation between server-side/build-time configuration and client-side runtime configuration. The GitHub PAT, which should only be used during the static site generation phase to fetch gist data from the GitHub API, was being passed through to the client-side JavaScript bundle without sanitization.

The fix introduces a clear architectural boundary between build-time and runtime configurations. The patched version implements a RuntimeConfig interface that explicitly excludes sensitive credentials, ensuring only safe configuration values like enabled, verbose, and component paths are accessible client-side.

Attack Vector

The attack vector is network-based and requires no authentication or user interaction. An attacker can exploit this vulnerability through the following steps:

  1. Navigate to any Docusaurus website using the vulnerable plugin
  2. Open browser developer tools or view page source
  3. Inspect the JavaScript bundles or search for configuration objects
  4. Extract the exposed GitHub Personal Access Token
  5. Use the stolen token to access the victim's GitHub account with whatever permissions the token grants

The patched code introduces proper client-server separation:

typescript
/**
 * Client-side plugin component
 * This runs in the browser and has access to runtime configuration only
 */

interface RuntimeConfig {
  enabled: boolean
  verbose: boolean
  gistListPageComponent: string
  gistPageComponent: string
}

class GistsClient {
  private config: RuntimeConfig

  constructor(config: RuntimeConfig) {
    this.config = config
  }

  // Client-side utility methods
  isEnabled(): boolean {
    return this.config.enabled
  }

  isVerbose(): boolean {
    return this.config.verbose
  }

  getGistListComponent(): string {
    return this.config.gistListPageComponent

Source: GitHub Commit Update

The fix also introduces a proper context provider pattern to manage configuration:

text
+import React, { createContext, useContext, ReactNode } from 'react'
+import { GistsClient, RuntimeConfig } from './index'
+
+interface GistsContextType {
+  client: GistsClient
+  config: RuntimeConfig
+}
+
+const GistsContext = createContext<GistsContextType | undefined>(undefined)
+
+interface GistsProviderProps {
+  children: ReactNode
+  config: RuntimeConfig
+}
+
+export function GistsProvider({ children, config }: GistsProviderProps) {
+  const client = new GistsClient(config)
+
+  return <GistsContext.Provider value={{ client, config }}>{children}</GistsContext.Provider>
+}
+
+export function useGists() {
+  const context = useContext(GistsContext)
+  if (context === undefined) {
+    throw new Error('useGists must be used within a GistsProvider')
+  }
+  return context
+}
+
+export function useGistsClient() {

Source: GitHub Commit Update

Detection Methods for CVE-2025-53624

Indicators of Compromise

  • Presence of GitHub Personal Access Tokens in client-side JavaScript bundle files
  • Configuration objects containing token, pat, or personalAccessToken fields in browser-accessible code
  • Unexpected GitHub API activity from unfamiliar IP addresses using your token
  • GitHub security alerts indicating token exposure or unusual authentication patterns

Detection Strategies

  • Audit JavaScript bundles in production builds by searching for strings matching PAT patterns (e.g., ghp_, github_pat_)
  • Review package.json and package-lock.json for docusaurus-plugin-content-gists versions below 4.0.0
  • Implement pre-deployment scans using secret detection tools like git-secrets, trufflehog, or gitleaks
  • Monitor GitHub's security tab for token exposure notifications

Monitoring Recommendations

  • Enable GitHub's token scanning and push protection features to detect exposed credentials
  • Set up alerts for GitHub API usage anomalies associated with your Personal Access Tokens
  • Implement Content Security Policy (CSP) reporting to detect unexpected script behaviors
  • Regularly audit production builds for sensitive data exposure using automated security scanning

How to Mitigate CVE-2025-53624

Immediate Actions Required

  • Upgrade docusaurus-plugin-content-gists to version 4.0.0 or later immediately
  • Rotate any GitHub Personal Access Tokens that may have been exposed in previous builds
  • Audit your production website's JavaScript bundles for exposed credentials
  • Review GitHub account activity for any unauthorized access during the exposure window
  • Invalidate and regenerate all PATs used with the vulnerable plugin version

Patch Information

The vulnerability is fixed in docusaurus-plugin-content-gists version 4.0.0. The patch introduces a proper separation between build-time and runtime configurations through a new RuntimeConfig interface and GistsClient class architecture. The fix ensures that sensitive credentials like GitHub PATs are only used during the build phase and are never serialized into client-side bundles.

For detailed information about the security fix, refer to the GitHub Security Advisory GHSA-qf34-qpr4-5pph and the security patch commit.

Workarounds

  • Remove the PAT from plugin configuration entirely and use unauthenticated GitHub API access (note: this has stricter rate limits)
  • Implement environment variable separation ensuring PATs are only available during build and not bundled
  • Use GitHub Actions or CI/CD pipelines to fetch gists at build time without passing tokens to the plugin
  • Temporarily disable the gists plugin until upgrade to version 4.0.0 is complete
bash
# Upgrade to patched version
npm update docusaurus-plugin-content-gists@^4.0.0

# Or with yarn
yarn upgrade docusaurus-plugin-content-gists@^4.0.0

# Verify installed version
npm list docusaurus-plugin-content-gists

# Rotate compromised GitHub PAT via GitHub CLI
gh auth refresh

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

  • Vulnerability Details
  • TypeInformation Disclosure

  • Vendor/TechDocusaurus

  • SeverityCRITICAL

  • CVSS Score10.0

  • EPSS Probability7.58%

  • Known ExploitedNo
  • CVSS Vector
  • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
  • Impact Assessment
  • ConfidentialityLow
  • IntegrityNone
  • AvailabilityHigh
  • CWE References
  • CWE-200
  • Technical References
  • GitHub Commit Update

  • GitHub Security Advisory GHSA-qf34-qpr4-5pph
  • Latest CVEs
  • CVE-2025-11956: OBS Student Affairs System XSS Flaw

  • CVE-2026-49199: Acer Predator Connect W6x Firmware RCE Flaw

  • CVE-2026-46344: Openquantumsafe Liboqs DOS Vulnerability

  • CVE-2026-44518: Openquantumsafe Liboqs DoS Vulnerability
Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.

Try SentinelOne
  • Get Started
  • Get a Demo
  • Product Tour
  • Why SentinelOne
  • Pricing & Packaging
  • FAQ
  • Contact
  • Contact Us
  • Customer Support
  • SentinelOne Status
  • Language
  • Platform
  • Singularity Platform
  • Singularity Endpoint
  • Singularity Cloud
  • Singularity AI-SIEM
  • Singularity Identity
  • Singularity Marketplace
  • Purple AI
  • Services
  • Wayfinder TDR
  • SentinelOne GO
  • Technical Account Management
  • Support Services
  • Verticals
  • Energy
  • Federal Government
  • Finance
  • Healthcare
  • Higher Education
  • K-12 Education
  • Manufacturing
  • Retail
  • State and Local Government
  • Cybersecurity for SMB
  • Resources
  • Blog
  • Labs
  • Case Studies
  • Videos
  • Product Tours
  • Events
  • Cybersecurity 101
  • eBooks
  • Webinars
  • Whitepapers
  • Press
  • News
  • Ransomware Anthology
  • Company
  • About Us
  • Our Customers
  • Careers
  • Partners
  • Legal & Compliance
  • Security & Compliance
  • Investor Relations
  • S Foundation
  • S Ventures

©2026 SentinelOne, All Rights Reserved.

Privacy Notice Terms of Use

English