dbcve.org
Vasion PrintApplication · Printerlogic

CVE-2025-27680

CRITICAL · 9.1 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to 1.0.750 / 20.0.1442 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 1.0.750 Application 20.0.1442 allows Insecure Firmware Image with Insufficient Verification of Data Authenticity V-2024-004.

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 Virtual Appliance before version 1.0.750 (Host) and 20.0.1442 (Application) contains an insecure firmware image vulnerability where the system insufficiently verifies the authenticity of firmware images, potentially allowing remote attackers to deploy malicious firmware due to missing or weak cryptographic verification of firmware integrity.

MitigationUpgrade Vasion Print Virtual Appliance Host to version 1.0.750 or later and Application to version 20.0.1442 or later to implement proper firmware image authenticity verification.

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.1442
Virtual ApplianceApplication
Affected:< 1.0.750

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
None

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

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 installed Printerlogic product
    Locate and inspect the installed Vasion Print or Printerlogic Virtual Appliance installation. Check for printer management services, print server components, or virtual appliance images running in your environment.
    Affected if The product is Printerlogic Vasion Print or Printerlogic Virtual Appliance
  2. Check Vasion Print application version
    Access the Vasion Print admin console or check the application bundle for its version number. Typically found in the application metadata, About section, or installed packages.
    Affected if Version is below 20.0.1442
  3. Check Virtual Appliance host version
    Access the Virtual Appliance management interface (VMware/Hyper-V console or admin portal) and identify the appliance version. Check the system information or version reporting within the appliance OS.
    Affected if Host version is below 1.0.750
  4. Verify firmware update capability status
    Examine if the firmware update or remote deployment feature is enabled and accessible. Check admin settings for firmware deployment, remote imaging, or device firmware management.
    Affected if Firmware update mechanism is accessible and in use on vulnerable versions

A user is affected if they have Printerlogic Vasion Print below version 20.0.1442 or Virtual Appliance host below version 1.0.750 running and the firmware update/deployment feature is accessible.

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 1.0.750 / 20.0.1442 or later
Fixed in 1.0.75020.0.1442
Interim mitigation

Upgrade Vasion Print Virtual Appliance Host to version 1.0.750 or later and Application to version 20.0.1442 or later to implement proper firmware image authenticity verification.

Recommended fix High confidence

Vasion Print 20.0.1442 or higher; Virtual Appliance 1.0.750 or higher

  1. 1. Identify the current version of Vasion Print by accessing the admin console or checking the application management interface
  2. 2. Identify the current version of Virtual Appliance by accessing the appliance management interface
  3. 3. If Vasion Print version is below 20.0.1442, upgrade to version 20.0.1442 or later
  4. 4. If Virtual Appliance version is below 1.0.750, upgrade to version 1.0.750 or later
  5. 5. After upgrading, verify the firmware/image verification functionality is working correctly
  6. 6. Confirm the installed versions match the secure releases (20.0.1442+ for Application, 1.0.750+ for Virtual Appliance)

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

Fix this in Vasion Print Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27680 — 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-27680 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