CVE-2025-27646
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.913 Application 20.0.2253 allows Edit User Account Exposure V-2024-001.
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 confidenceVasion Print (formerly PrinterLogic) contains an information disclosure vulnerability in the user account editing functionality. The vulnerability allows unauthorized access or exposure of sensitive user account data through the edit user account feature in versions prior to Virtual Appliance Host 22.0.913 and Application 20.0.2253. The critical CVSS score indicates unauthenticated network attackers can exploit this to access or modify sensitive account information.
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.2253< 22.0.913CVSS 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.
-
Identify the product typeDetermine whether your installation is the PrinterLogic Virtual Appliance (standalone appliance) or the Vasion Print Application (deployed on your own infrastructure)Affected if N/A - this step identifies which version threshold applies
-
Check Virtual Appliance versionIf using Virtual Appliance, access the appliance admin panel or check the version displayed in the Virtual Appliance Host management interfaceAffected if The installed version is below 22.0.913
-
Check Application versionIf using the Application variant, check the version number in the application's About or Admin settings pageAffected if The installed version is below 20.0.2253
-
Compare version against thresholdsVerify the exact installed version number matches or exceeds the fixed releases (22.0.913 for Virtual Appliance, 20.0.2253 for Application)Affected if The installed version is below the applicable threshold for your product type
Your environment is affected if you are running PrinterLogic Virtual Appliance Host below version 22.0.913 or Vasion Print Application below version 20.0.2253.
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.225322.0.913
Upgrade to Virtual Appliance Host version 22.0.913 or higher and Application version 20.0.2253 or higher. If immediate patching is not possible, restrict network access to the management interface and monitor for unauthorized account access attempts.
Virtual Appliance Host 22.0.913 with Application 20.0.2253
- Verify current Vasion Print (PrinterLogic) version in the admin console or system information
- Download Virtual Appliance Host version 22.0.913 or later
- Download Application version 20.0.2253 or later
- Backup current configuration and database according to vendor backup procedures
- Apply the upgrade following Vasion's standard upgrade documentation
- Verify the upgrade was successful by checking the version numbers post-upgrade
- Test that user account management functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27646 — 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-27646 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