CVE-2025-64711
LowCVSS 3.9Exploitation Probability (EPSS)
Low risk2th percentile - higher than 2% of all known CVEs
Summary
A self-XSS vulnerability in PrivateBin allows a filename containing HTML to be reflected verbatim into the page via the drag-and-drop helper. A macOS or Linux user who drags a crafted file into the editor executes arbitrary JavaScript within their own session. File upload must be enabled and user interaction is required.
Risk Assessment
An attacker can exfiltrate plaintext, passphrases, or encryption keys before data is encrypted, defeating zero-knowledge guarantees for that victim session. If CSP is disabled, HTML injection attacks such as redirects to foreign websites or phishing may also be possible.
Recommendation
Update PrivateBin to version 2.0.3 or later, which patches the issue. Additionally, ensure that Content-Security-Policy (CSP) is enabled and properly configured.
Other vulnerabilities in PrivateBin
See all- CVE-2026-55891Unknown
PrivateBin before version 2.0.5 has a vulnerability in Request::getRequestUri() which passes $_SERVER['REQUEST_URI'] through FILTER_SANITIZE_URL, not removing quotation marks, angle brackets, or apostrophes. The attacker-controlled value is then inserted into JSON-LD templates without JSON escaping, potentially allowing injection of data into application/ld+json responses.
- CVE-2026-55696Medium
PrivateBin is an online pastebin where the server has zero knowledge of pasted data. Prior to 2.0.5, AttachmentViewer.setAttachment in js/privatebin.js uses getAttachmentMimeType to accept attacker-controlled MIME types and uses getBlobUrl to create a same-origin blob before setting attachmentLink's href for the Download attachment link. The SVG-only sanitization branch updates only the preview blob, so text/html, image/svg, application/xhtml+xml, and text/xml attachments can remain active in the download blob. On an instance with fileupload = true and a weakened, stripped, or absent Content Security Policy, an anonymous attacker can create such an attachment, and a victim who opens the link in a new tab causes inline JavaScript to execute in the PrivateBin origin. The script can read origin-scoped local storage and issue same-origin requests, including requests to applications co-hosted on the same domain. This issue is fixed in version 2.0.5.
- CVE-2025-64714Medium
PrivateBin versions 1.7.7 through before 2.0.3 contain an unauthenticated Local File Inclusion in the template-switching feature. If templateselection is enabled, the server trusts the template cookie and includes the referenced PHP file, potentially allowing sensitive data disclosure or remote code execution. Fixed in version 2.0.3; workaround is to set templateselection = false.
- CVE-2025-62796Medium
PrivateBin is an online pastebin with zero knowledge of pasted data. Versions 1.7.7 through 2.0.1 allow persistent HTML injection via the unsanitized attachment filename (attachment_name) when attachments are enabled. An attacker can modify attachment_name before encryption so that, after decryption, arbitrary HTML is inserted unescaped near the file size hint, enabling redirects and site defacement and related phishing attacks. Script execution is normally blocked by the recommended CSP.
Original NVD description (English source)
PrivateBin is an online pastebin where the server has zero knowledge of pasted data. Starting in version 1.7.7 and prior to version 2.0.3, 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. Certain conditions must exist for the vulnerability to be exploitable. Only macOS 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. Any Mac / Linux user who can be tricked into dragging a maliciously named file into the editor is impacted; code runs in the origin of the PrivateBin instance they are using. Attackers can steal plaintext, passphrases, or manipulate the UI before data is encrypted, defeating the zero-knowledge guarantees for that victim session, assuming counter-measures like Content-Security-Policy (CSP) have been disabled. If CSP is not disabled, HTML injection attacks may be possible - like redirecting to a foreign website, phishing etc. 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. Version 2.0.3 patches the issue.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS