Skip to main content
VulnerabilityPublished Updated

CVE-2025-64711: privatebin/privatebin · PrivateBin vulnerable to malicious filename use for self-XSS / HTML injection locally for users

Affects privatebin/privatebinSource GCVE Database

0
Compare

Not known to be exploited · CVSS 3.9 Low : upgrade to 2.0.3 when convenient.

Data as of 19 Nov 2026, 02:52 UTC

CVSS 3.1 base score
3.9Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.0.3
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  5. 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 18 Nov 2026.

What to do

Upgrade privatebin/privatebin to 2.0.3.

Affected software

ProductAffectedFixed in
Packagistprivatebin/privatebinAffected
  • >=1.7.7 <2.0.3
Fixed in
  • 2.0.3

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

AI-suggested

Upgrade PrivateBin to version 2.0.3 or later, where the vulnerability is fixed. Ensure that a strong Content-Security-Policy (CSP) header is configured and enforced to prevent script execution from injected HTML. Verify that CSP settings are not overridden by web servers, proxies, or CDNs. Alternatively, disable file attachments in PrivateBin to prevent the vulnerability. Deploying PrivateBin on a separate domain can also limit the impact of this vulnerability. Users should independently verify CSP effectiveness even after upgrading.

Description

PrivateBin versions from 1.7.7 up to but not including 2.0.3 have a vulnerability where filenames containing HTML can be injected via drag-and-drop file uploads. This leads to self-XSS (cross-site scripting) for Mac and Linux users who drag maliciously named files into the editor, allowing arbitrary JavaScript execution in their session. The vulnerability requires file upload enabled and user interaction to attach the crafted file. Windows users are not affected due to filename restrictions. The vulnerability is mitigated by Content-Security-Policy (CSP) headers, which most instances use. The issue is patched in version 2.0.3.

References

Community reviews

Loading reviews…