CVE-2025-64714
BaseFortify
Publication date: 2025-11-13
Last updated on: 2025-11-13
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| privatebin | privatebin | 2.0.3 |
| privatebin | privatebin | 1.7.7 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-98 | The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. |
| CWE-73 | The product allows user input to control or influence paths or file names that are used in filesystem operations. |
| CWE-23 | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an unauthenticated Local File Inclusion (LFI) in PrivateBin versions from 1.7.7 up to before 2.0.3. It occurs in the template-switching feature when the 'templateselection' setting is enabled. The server trusts the 'template' cookie and includes the referenced PHP file without proper validation. This can allow an attacker to read sensitive data or, if they can place a malicious PHP file on the server, execute remote code. The vulnerability arises because the server includes files based on user input without sufficient privilege checks or protections. It has been fixed in version 2.0.3, and a workaround is to disable 'templateselection' in the configuration.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to read sensitive data stored on the server or potentially execute arbitrary code remotely if they manage to upload a malicious PHP file. This could lead to unauthorized access to confidential information or full compromise of the server hosting PrivateBin.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, set `templateselection = false` in the `cfg/conf.php` configuration file or remove the `templateselection` setting entirely. This disables the vulnerable template-switching feature. Additionally, upgrade PrivateBin to version 2.0.3 or later where the issue is patched.