Answer in brief
CVE-2025-34210 records a Critical severity (CVSS 9.4) vulnerability in Vasion Print (formerly PrinterLogic) Readable Cleartext Passwords. The current sources do not mark it as known exploited. The current feed maps Vasion/Print Application (generic), Vasion/Print Virtual Appliance Host (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Vasion/Print Application (generic), Vasion/Print Virtual Appliance Host (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:vasion:virtual_appliance_application:-:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:a:vasion:virtual_appliance_host:-:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Vasion/Print Applicationgeneric | 0 | Not reported |
| Vasion/Print Virtual Appliance Hostgeneric | 0 | Not reported |
Published upstream
Oct 2, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
Vasion Print (formerly PrinterLogic) Virtual Appliance Host and Application (VA/SaaS deployments) store a large number of sensitive credentials (database passwords, MySQL root password, SaaS keys, Portainer admin password, etc.) in cleartext files that are world-readable. Any local user - or any process that can read the host filesystem - can retrieve all of these secrets in plain text, leading to credential theft and full compromise of the appliance. The vendor does not consider this to be a security vulnerability as this product "follows a shared responsibility model, where administrators are expected to configure persistent storage encryption."
Quoted source text, attributed separately from HOL analysis.