dbcve.org
Vasion PrintApplication · Printerlogic

CVE-2025-27683

HIGH · 8.8 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to 1.0.735 / 20.0.1330 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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.735 Application 20.0.1330 allows Driver Unrestricted Upload of File with Dangerous Type V-2022-006.

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) before Virtual Appliance Host 1.0.735 and Application 20.0.1330 contains an unrestricted file upload vulnerability in the driver upload functionality (V-2022-006). An authenticated attacker can upload malicious files (likely DLLs, executables, or other dangerous driver-related file types) without proper validation, potentially achieving remote code execution with the application's privileges.

MitigationUpgrade to Virtual Appliance Host version 1.0.735 or later and Application version 20.0.1330 or later to obtain the patched build. If immediate patching is not possible, restrict network access to the management interface and monitor for suspicious file uploads.

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.1330
Virtual ApplianceApplication
Affected:< 1.0.735

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Check the Vasion Print Application version
    Access the application's admin interface or check the installed package version. Look for a version indicator in the About section or system information page.
    Affected if The installed application version is below 20.0.1330
  2. Check the Virtual Appliance Host version
    Access the virtual appliance management console or check the appliance's system information. Look for the host/virtual appliance version number.
    Affected if The installed Virtual Appliance version is below 1.0.735
  3. Verify if driver upload functionality is accessible
    Log into the application as an authenticated user and navigate to the driver management or driver upload section. Determine if the driver upload feature is present and accessible.
    Affected if The driver upload feature is available to authenticated users without additional security restrictions
  4. Inspect uploaded driver files location
    If you have access to the file system, examine the directory where driver files are stored. Look for file types that should not be present such as .exe, .dll, .ps1, or other executable formats.
    Affected if Executable or script files are found in the driver upload directory that do not match expected driver file types

You are affected if your Vasion Print application version is below 20.0.1330 or your Virtual Appliance version is below 1.0.735, and authenticated users can access the driver upload functionality.

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.735 / 20.0.1330 or later
Fixed in 1.0.73520.0.1330
Interim mitigation

Upgrade to Virtual Appliance Host version 1.0.735 or later and Application version 20.0.1330 or later to obtain the patched build. If immediate patching is not possible, restrict network access to the management interface and monitor for suspicious file uploads.

Recommended fix High confidence

Vasion Print 20.0.1330 or higher; Virtual Appliance 1.0.735 or higher

  1. 1. Back up the current Vasion Print/Virtual Appliance configuration and data before upgrading.
  2. 2. Navigate to the Vasion Print admin console or access the Virtual Appliance management interface.
  3. 3. Download the latest version from help.printerlogic.com or the vendor's official download portal.
  4. 4. For Virtual Appliance: Upgrade to version 1.0.735 or higher following the vendor's upgrade documentation.
  5. 5. For Vasion Print Application: Upgrade to version 20.0.1330 or higher.
  6. 6. After upgrade, verify the application starts successfully and all services are running.
  7. 7. Confirm the unrestricted file upload vulnerability (CWE-434) is remediated by testing that driver uploads are properly validated.
Caveat Review release notes for any deprecations or migration requirements specific to your current version

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

Fix this in Vasion Print Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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