# CVE-2025-64714: PrivateBin's template-switching feature allows arbitrary local file inclusion through path traversal

> Unauthenticated attackers can exploit path traversal in the template-switching feature to read sensitive files or execute code if template selection is enabled.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-g2j9-g8r5-rg82

## What is CVE-2025-64714?

CVE-2025-64714 is a medium-severity path traversal vulnerability in PrivateBin, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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, an unauthenticated Local File Inclusion exists in the template-switching feature. If `templateselection` is enabled in the configuration, the server trusts the `template` cookie and includes the referenced PHP file. An attacker can read sensitive data or, if they manage to drop a PHP file elsewhere, gain remote code execution. The constructed path of the template file is checked for existence, then included. For PrivateBin project files this does not leak any secrets due to data files being created with PHP code that prevents execution, but if a configuration file without that line got created or the visitor figures out the relative path to a PHP script that directly performs an action without appropriate privilege checking, those might execute or leak information. The issue has been patched in version 2.0.3. As a workaround, set `templateselection = false` (which is the default) in `cfg/conf.php` or remove it entirely

Weakness: CWE-73 (External Control of File Name or Path), CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program), CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2025-64714?

2 open source packages ship an affected version, including privatebin/privatebin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `privatebin/privatebin` | Packagist | From 1.7.7 | 2.0.3 |
| `privatebin/privatebin` | Packagist | From 1.7.7 | 2.0.3 |

## How do I fix CVE-2025-64714?

Upgrade privatebin/privatebin to 2.0.3 or later.

## Is CVE-2025-64714 being exploited?

There is no known exploitation of CVE-2025-64714 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Medaz-Sploit/CVE-2025-64714-privatebin-2.0.2-PoC (github_poc): https://github.com/Medaz-Sploit/CVE-2025-64714-privatebin-2.0.2-PoC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64714 and fix it if it is affected.

What it is: CVE-2025-64714 is a medium-severity path traversal vulnerability in PrivateBin, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64714 in the wild and no public exploit code.

Affected packages and fixed versions:
- privatebin/privatebin (Packagist): affected from 1.7.7; fixed in 2.0.3
- privatebin/privatebin (Packagist): affected from 1.7.7; fixed in 2.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64714/ (Markdown: https://insights.sbomify.com/CVE-2025-64714/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64714
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64714
- OSV: https://osv.dev/vulnerability/CVE-2025-64714

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64714/
Summaries are generated and may contain mistakes; the official description above is the record.