CVE-2025-64711

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 name on Windows.
• The PrivateBIn instance needs to have file upload enabled.
• An attacker needs to have access to the local file system or somehow convince the user to create (or download) a malicious file (name).
• An attacker needs to convince the user to attach that malicious file to PrivateBin.

Real-life impact

As the whole exploit needs to be included in the file name of the attached file and only affects the local session of the user (aka it is neither persistent nor remotely executable) and that user needs to interact and actively attach that file to the paste, the impact is considered to be practically low.

Technical Description

When a file is dropped, readFileData collects all filenames and calls printDragAndDropFileNames:

const fileNames = loadedFiles.map((loadedFile => loadedFile.name));
printDragAndDropFileNames(fileNames);

printDragAndDropFileNames then renders those names:

        function printDragAndDropFileNames(fileNames) {
            $dragAndDropFileNames.html(fileNames.join('<br>'));
        }

This will insecurely render the user-submitted filenames as HTML.

This vulnerability has been introduced in this commit (introduced in 1.7.7).

The previous render method was using .text():

$dragAndDropFileName.text(loadedFile.name);

Reproduction Steps

1. On a Unix-like system, create a file with an HTML/JS payload in its name, e.g. by running touch '"><img src=x onerror=alert(document.domain)>.txt'.
2. Deploy or use any PrivateBin instance with attachments enabled (including https://privatebin.net/).
3. Open the UI in a browser and start a new paste.
4. Drag the crafted file anywhere on the page
5. As soon as it is dropped, the filename is inserted into #dragAndDropFileName as HTML and the onerror handler fires (assuming CSP is disabled), showing the alert.

Mitigation

PrivateBin strongly recommends users to upgrade to the latest release. However, here are some workarounds that may help users to mitigate this vulnerability without upgrade:

• Update the CSP in your configuration file to the latest recommended settings and check that it isn't getting reverted or overwritten by the web server, reverse proxy or CDN, i.e. using PrivateBin's offered check service.
  Note: Users should check the CSP independently, even if they've upgrade to a fixed version.
• Deploying PrivateBin on a separate domain may limit the scope of the vulnerability to PrivateBin itself and thus, as described in the “Impact” section, effectively prevent any damage by the vulnerability to other resources users are hosting.
• As explained in the impact assessment, disabling attachments also prevents this issue.

Credits

PrivateBin would like to thank Benoit Esnard, who reported this vulnerability.

In general, PrivateBin would like to thank everyone reporting issues and potential vulnerabilities.

If a user thinks they have found a vulnerability or potential security risk, PrivateBin would kindly ask you to follow our security policy and report it. PrivateBin will then assess the report and will take the necessary actions to address it.

Timeline

• 2025-11-09 Received report via GitHub Security Advisory
• 2025-11-10 Discussed and reproduced issue, created a patch
• 2025-11-11 Further work on patch
• 2025-11-12 Released patch with PrivateBin 2.0.3