CVE-2025-27655
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.862 Application 20.0.2014 allows Server-Side Request Forgery: CPA v1 V-2023-009.
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 confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in Vasion Print (formerly PrinterLogic) that allows attackers to make the server perform unintended requests to internal or external resources, potentially accessing sensitive internal services or bypassing network restrictions.
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.2014< 22.0.862CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Vasion Print application versionLog into the PrinterLogic/Vasion Print admin web interface and navigate to Administration > About or Help > About. The version is displayed on this page.Affected if The version displayed is less than 20.0.2014
-
Check Virtual Appliance versionAccess the Virtual Appliance management interface (VMware vSphere Client, Hyper-V Manager, or the appliance's own admin portal) and locate the VM or appliance version information. Alternatively, access the appliance's admin panel and check System > About or similar.Affected if The Virtual Appliance version is less than 22.0.862
-
Verify version through installed softwareIf installed on a Windows server, open Programs and Features (appwiz.cpl) and locate 'Vasion Print' or 'PrinterLogic' in the installed programs list to see the exact version number.Affected if The installed software version is less than 20.0.2014
A system is affected if the Vasion Print application version is below 20.0.2014 or the Virtual Appliance version is below 22.0.862, regardless of configuration, because this is a version-dependent vulnerability in the application's request handling functionality.
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.201422.0.862
Upgrade to Virtual Appliance Host 22.0.862 or later and Application 20.0.2014 or later to remediate this vulnerability.
Virtual Appliance Host 22.0.862 / Application 20.0.2014
- 1. Identify the current version of Vasion Print (PrinterLogic) installation in your environment
- 2. If running Virtual Appliance, upgrade to version 22.0.862 or higher
- 3. If running the Application component, upgrade to version 20.0.2014 or higher
- 4. After upgrade, verify the SSRF vulnerability is no longer present by reviewing application logs for any anomalous requests
- 5. Confirm normal printing and management functionality continues to work as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27655 — 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-27655 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