CVE-2025-27637
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 · uneditedVasion Print (formerly PrinterLogic) before Virtual Appliance Host 22.0.1002 Application 20.0.2614 allows Cross-Site Scripting V-2024-016.
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 confidenceVasion Print (formerly PrinterLogic) contains a Cross-Site Scripting (XSS) vulnerability in versions prior to Virtual Appliance Host 22.0.1002 and Application 20.0.2614. This allows attackers to inject malicious scripts into web pages that are viewed by other users, potentially stealing session cookies or performing actions on behalf of authenticated users.
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< 20.0.2614< 22.0.1002CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check Virtual Appliance Host versionLog in to the Vasion Print Virtual Appliance admin interface and navigate to the System Settings or About page to view the host version numberAffected if version is lower than 22.0.1002
-
Check Application versionLog in to the Vasion Print Application web portal and locate the version information typically found in the Help, About, or Settings sectionAffected if version is lower than 20.0.2614
-
Verify both componentsConfirm that both the Virtual Appliance Host and Application components are installed, as the XSS vulnerability applies when either component is present in an affected versionAffected if either component is below its respective version threshold
You are affected if either your Virtual Appliance Host version is below 22.0.1002 or your Application version is below 20.0.2614.
Generated from the published advisory. Verify against your own configuration.
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 · scoped20.0.261422.0.1002
Upgrade Vasion Print Virtual Appliance Host to version 22.0.1002 or later and Application to version 20.0.2614 or later. Additionally, implement output encoding and input validation on all user-supplied data fields as a defense-in-depth measure.
Vasion Print Application 20.0.2614 and Virtual Appliance Host 22.0.1002
- 1. Create a complete backup of the current Vasion Print configuration and database
- 2. Download Vasion Print Application version 20.0.2614 or later from the official Vasion support portal at help.printerlogic.com
- 3. Download Virtual Appliance Host version 22.0.1002 or later
- 4. Apply the Virtual Appliance Host upgrade first, following the vendor's documented upgrade procedure
- 5. Apply the Vasion Print Application upgrade (20.0.2614 or later)
- 6. Verify the upgrade completed successfully by checking the version numbers in the admin console
- 7. Test that the application functions normally after upgrade
- 8. Validate that the XSS vulnerability V-2024-016 is resolved by testing the previously vulnerable input fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27637 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27637 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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