CVE-2025-64714

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.8 from GitHub Security Advisory (severity: MODERATE) published 2025-11-14. A secondary CVSS source baseline 5.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2025-175312 (ENISA EUVD) · GHSA-g2j9-g8r5-rg82 (GitHub Security Advisories)Source: ENISA EUVD

5.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
5.8
EG Score
5.8MEDIUMmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity58% × 45%
Impact severity (EG Severity): CVSS 5.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.8): severity, escalated by confirmed exploitation. This CVE's 5.8 is its impact severity (EG Severity), not escalated.

EG Severity
5.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 13, 2025

Last Modified

October 19, 2026

Advisory Details (2)

Auto-updated Oct 19, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Template-switching feature allowing arbitrary local file inclusion through path traversal · Advisory · PrivateBin/PrivateBin · GitHub

Affected: version 2.0.3.

https://github.com/PrivateBin/PrivateBin/security/advisories/GHSA-g2j9-g8r5-rg82
GitHub commit Patch Available

commit 4434dbf73ac5 (PrivateBin/PrivateBin)

Patch available: PrivateBin/PrivateBin 2.0.3 (contains commit 4434dbf73ac5)

https://github.com/PrivateBin/PrivateBin/commit/4434dbf73ac53217fda0f90d8cf9b6110f8acc4f

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerprivatebin/privatebin @ 2.0.3 (fixes >= 1.7.7, < 2.0.3)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
privatebin/privatebin1.7.7 ... 2.0.2 (6 versions)
  • 1.7.7 up to 2.0.3: fixed in 2.0.3
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 225 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-11-01 08:02 UTCGHSA enrichmentGHSA-g2j9-g8r5-rg82 · GitHub severity MODERATE · GitHub CVSS 5.8
  4. 2026-11-01 08:02 UTCEG score recompute
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-28 10:55 UTCOSV refresh
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-10-25 16:10 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-19 13:27 UTCEG score recompute
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-18 05:20 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 70 more
  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-12 16:49 UTCEG score recompute
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-11 20:24 UTCEG score recompute
  6. 2026-10-11 18:36 UTCEG score recompute
  7. 2026-10-11 15:10 UTCEG score recompute
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-06 05:45 UTCOSV refresh
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  27. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  28. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  29. 2026-09-16 13:50 UTCOSV refresh
  30. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  37. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  38. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  39. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  40. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  41. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  42. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  43. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  44. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  45. 2026-08-28 13:23 UTCOSV refresh
  46. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  47. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  48. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  49. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  50. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  51. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  52. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  53. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  54. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  55. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  56. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  57. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  58. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  59. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  60. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  61. 2026-08-12 01:39 UTCOSV refresh
  62. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  63. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  64. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  65. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  66. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  67. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  68. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  69. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  70. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.5% · 39th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCMedaz-Sploit/CVE-2025-64714-privatebin-2.0.2-PoC
    Published May 7, 2026
    Open source ↗

Frequently asked(5)

What is CVE-2025-64714?
CVE-2025-64714 is a medium-severity vulnerability; its CVE record was published on November 13, 2025. 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…
When was the CVE record for CVE-2025-64714 published?
The CVE record for CVE-2025-64714 was published on November 13, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-64714 actively exploited?
CVE-2025-64714 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-64714?
CVE-2025-64714 has a CVSS base score of 5.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-64714?
A fix for CVE-2025-64714 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-64714

Explore →

Is Your Infrastructure Affected by CVE-2025-64714?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.