dbcve.org
Vasion PrintApplication · Printerlogic

CVE-2025-27642

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to 20.0.2368 / 22.0.933 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vasion Print (formerly PrinterLogic) before Virtual Appliance Host 22.0.933 Application 20.0.2368 allows Unauthenticated Driver Package Editing V-2024-008.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vasion Print (formerly PrinterLogic) contains an unauthenticated driver package editing vulnerability allowing remote attackers to modify print driver configurations without authentication. The vulnerability affects versions prior to Virtual Appliance Host 22.0.933 and Application 20.0.2368, with a critical CVSS 9.8 score indicating severe potential impact including remote code execution or complete system compromise.

MitigationUpgrade Vasion Print Virtual Appliance Host to version 22.0.933 or later AND Application to version 20.0.2368 or later to remediate this unauthenticated driver package editing vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vasion PrintApplication
Affected:< 20.0.2368
Virtual ApplianceApplication
Affected:< 22.0.933

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Vasion Print or PrinterLogic installation
    Check for the Virtual Appliance running (VMware/Hyper-V) or look for the PrinterLogic service on the network. The product typically exposes a web admin interface on port 443.
    Affected if The product is installed and running on the network.
  2. Check Virtual Appliance Host version
    Log into the Virtual Appliance admin interface and navigate to Administration > System Overview, or run 'plc --version' via SSH to the appliance. Compare against 22.0.933.
    Affected if Virtual Appliance Host version is below 22.0.933.
  3. Check Application version
    In the admin console, go to Administration > System Overview or check the version displayed on the login page. Compare against 20.0.2368.
    Affected if Application version is below 20.0.2368.
  4. Verify network exposure of admin interface
    Confirm whether the Virtual Appliance web interface (typically on port 443) is accessible from untrusted networks or the internet. Check firewall rules and NAT configurations.
    Affected if The admin interface is accessible from untrusted networks without VPN or authentication barriers.

The environment is affected if Vasion Print/PrinterLogic is running with Virtual Appliance Host below 22.0.933 or Application below 20.0.2368, and the interface is network-accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 20.0.2368 / 22.0.933 or later
Fixed in 20.0.236822.0.933
Interim mitigation

Upgrade Vasion Print Virtual Appliance Host to version 22.0.933 or later AND Application to version 20.0.2368 or later to remediate this unauthenticated driver package editing vulnerability.

Recommended fix High confidence

Application 20.0.2368 or later; Virtual Appliance Host 22.0.933 or later

  1. 1. Identify the current version of Vasion Print (PrinterLogic) by accessing the admin console or checking the Virtual Appliance host version
  2. 2. Navigate to the Vasion Print admin interface and locate the version information under System Settings or About
  3. 3. If the Application version is below 20.0.2368 OR the Virtual Appliance host version is below 22.0.933, the system is vulnerable
  4. 4. Obtain the latest stable release from the official Vasion/PrinterLogic download portal or contact Vasion support
  5. 5. Backup the current configuration and database before performing the upgrade
  6. 6. Apply the upgrade to the Virtual Appliance Host first (target version 22.0.933 or later)
  7. 7. Apply the Application update (target version 20.0.2368 or later)
  8. 8. After upgrade, verify the version numbers reflect the fixed releases
Caveat Test the upgrade in a staging environment first as major version upgrades may introduce configuration or compatibility changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vasion Print Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27642 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27642 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data