Vasion PrintApplication · Printerlogic

CVE-2025-27660

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to 20.0.1923 / 22.0.843 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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.843 Application 20.0.1923 allows Cross Site Scripting OVE-20230524-0003.

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 · moderate confidence

Cross-Site Scripting (XSS) vulnerability in Vasion Print (formerly PrinterLogic) allows attackers to inject malicious scripts through user inputs. The vulnerability exists in versions prior to Virtual Appliance Host 22.0.843 and Application 20.0.1923, potentially compromising other users viewing the injected content.

MitigationUpgrade Vasion Print Virtual Appliance Host to version 22.0.843 or later and Application to version 20.0.1923 or later to remediate this XSS 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.1923
Virtual ApplianceApplication
Affected:< 22.0.843

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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. Check Virtual Appliance Host version
    Log into the PrinterLogic/Vasion Print admin console and navigate to Administration > System > About, or check the appliance's web interface for the build/version number displayed on the login page or in the system information section.
    Affected if The displayed version is lower than 22.0.843 (e.g., 22.0.800, 21.x.x, etc.)
  2. Check Vasion Print Application version
    In the admin console, go to Administration > Application > About, or access the Windows/macOS client application and check Help > About for the version number.
    Affected if The displayed version is lower than 20.0.1923 (e.g., 20.0.1500, 19.x.x, etc.)
  3. Verify both components if running hybrid deployment
    If using both the Virtual Appliance and the desktop client/application, ensure BOTH components are checked separately as each has its own version numbering and both are required to be patched.
    Affected if Either component is below its respective threshold (Virtual Appliance < 22.0.843 OR Application < 20.0.1923)

Your environment is affected if either the Virtual Appliance Host version is below 22.0.843 or the Application version is below 20.0.1923, as both product lines are independently vulnerable to the XSS flaw.

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.1923 / 22.0.843 or later
Fixed in 20.0.192322.0.843
Interim mitigation

Upgrade Vasion Print Virtual Appliance Host to version 22.0.843 or later and Application to version 20.0.1923 or later to remediate this XSS vulnerability.

Recommended fix High confidence

Vasion Print 20.0.1923 / Virtual Appliance Host 22.0.843 or later releases

  1. Identify your current Vasion Print (PrinterLogic) version in the admin console or system information
  2. Navigate to the Vasion support or download portal to obtain the latest release
  3. Upgrade Vasion Print to version 20.0.1923 or higher
  4. Upgrade Virtual Appliance Host to version 22.0.843 or higher
  5. After upgrading, verify the XSS vulnerability is resolved by reviewing release notes or performing a security scan
  6. Confirm all admin and client browsers clear any cached sessions to avoid stale cookie issues

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-27660 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