Skip to main content
CVE-2025-53624VulnerabilityPublished

CVE-2025-53624: webbertakken docusaurus-plugin-content-gists · Information Exposure

Affects webbertakken docusaurus-plugin-content-gistsSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 10.0 Critical : upgrade to 4.0.0 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.0% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jul 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade webbertakken docusaurus-plugin-content-gists to 4.0.0.

Affected software

ProductAffectedFixed in
npmdocusaurus-plugin-content-gistspkg:npm/docusaurus-plugin-content-gistsOther threatsAffected
  • <4.0.0
Fixed in
  • 4.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade docusaurus-plugin-content-gists to version 4.0.0 or later, which contains the fix that prevents Personal Access Tokens from being included in client-side bundles. Until the upgrade is applied, organizations should audit their Docusaurus sites for the presence of exposed tokens by inspecting the JavaScript bundles and source code served to clients. Any exposed tokens should be considered compromised and revoked immediately in GitHub, followed by issuing new tokens with minimal necessary scopes. Organizations should also review their build and deployment pipelines to ensure that sensitive tokens are never injected into client-side code or publicly accessible artifacts. Implementing environment variable management and secret scanning tools in CI/CD pipelines can help detect accidental token exposures early. Additionally, adopting the principle of least privilege for GitHub tokens—limiting scopes strictly to what is necessary for the build process—reduces potential damage if exposure occurs. Monitoring GitHub audit logs for unusual activity related to token usage is recommended to detect potential exploitation attempts. Finally, educating developers and DevOps teams about secure handling of secrets in static site generators and build tools will help prevent recurrence.

Description

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.

References

Community reviews

Loading reviews…