PrivateBin vulnerable to malicious filename use for self-XSS / HTML injection locally for users

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.9 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

EPSS

• CVE-2025-64711: 0.13% estimated exploitation activity in the next 30 days; percentile 2.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Dragging a file whose filename contains HTML is reflected verbatim into the page via the drag-and-drop helper, so any user who drops a crafted file on PrivateBin will execute arbitrary JavaScript within their own session (self-XSS). This allows an attacker who can entice a victim to drag or otherwise attach such a file to exfiltrate plaintext, encryption keys, or stored pastes before they are encrypted or sent. Note 1: as the malicious filename must contain the character, the victim must not be using Windows for this to work, since this OS simply forbids this character in filenames. Note 2: most PrivateBin instances use the Content-Security-Policy header to prevent most use-cases of this vulnerability. This report will describe the impact as if this header had been disabled by the PrivateBin instance owner. Affected versions PrivateBin versions since 1.7.7 and before 2.0.3. Conditions Only macIOS or Linux users are affected, due to the way the character is treated in a file…

Published by the source

14 Nov 2025, 20:33 UTC

Last modified by the source

27 Nov 2025, 08:46 UTC

Source last checked

26 Oct 2026, 14:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r9x7-7ggj-fx9f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64711

Advisory: PrivateBin vulnerable to malicious filename use for self-XSS / HTML injection locally for users
IDs: CVE-2025-64711, GHSA-r9x7-7ggj-fx9f
Record: https://patchnext.com/advisories/cve-2025-64711 (revision 1, source checked 26 Oct 2026, 14:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: privatebin/privatebin 2.0.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist privatebin/privatebin: affected >= 1.7.7, < 2.0.3; fixed in 2.0.3

## Suggested inspection (read-only)
- Packagist privatebin/privatebin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on privatebin/privatebin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r9x7-7ggj-fx9f (GitHub-reviewed advisory GHSA-r9x7-7ggj-fx9f lists affected ranges: Packagist privatebin/privatebin >=1.7.7 <2.0.3)

Commands are suggestions: review each one before running it.