PrivateBin's template-switching feature allows arbitrary local file inclusion through path traversal

Exploitation

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

CVSS

5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2025-64714: 0.53% estimated exploitation activity in the next 30 days; percentile 44.79 (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 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 RCE. Affected versions PrivateBin versions since 1.7.7. Conditions - templateselection got enabled in cfg/conf.php - Visitor sets a cookie template pointing to an existing PHP file without it's suffix, using a path relative to the tpl folder. Absolute paths do not work. Impact 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,…

Published by the source

14 Nov 2025, 20:33 UTC

Last modified by the source

14 Nov 2025, 20:33 UTC

Source last checked

26 Oct 2026, 14:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g2j9-g8r5-rg82

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

# Patch Next advisory brief: CVE-2025-64714

Advisory: PrivateBin's template-switching feature allows arbitrary local file inclusion through path traversal
IDs: CVE-2025-64714, GHSA-g2j9-g8r5-rg82
Record: https://patchnext.com/advisories/cve-2025-64714 (revision 1, source checked 26 Oct 2026, 14:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
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-g2j9-g8r5-rg82 (GitHub-reviewed advisory GHSA-g2j9-g8r5-rg82 lists affected ranges: Packagist privatebin/privatebin >=1.7.7 <2.0.3)

Commands are suggestions: review each one before running it.