CVE-2025-27647
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 Addition of Partial Admin Users Without Authentication V-2024-002.
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 confidenceAn authentication bypass vulnerability in Vasion Print (formerly PrinterLogic) allows unauthenticated remote attackers to create partial administrative user accounts. The flaw affects Virtual Appliance Host versions prior to 22.0.913 and Application versions prior to 20.0.2253.
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.
-
Check Vasion Print Application versionLog into the PrinterLogic/Vasion Print admin console and navigate to the About or System Information page to view the installed Application version, or run 'pl-ctl status' via SSH to the applianceAffected if Application version is lower than 20.0.2253
-
Check Virtual Appliance Host versionAccess the Virtual Appliance management interface or run 'pl-ctl version' via SSH to determine the Virtual Appliance Host versionAffected if Virtual Appliance Host version is lower than 22.0.913
-
Audit administrator accountsReview the Users or Administrators panel in the admin console for any unauthorized or unexpected admin accounts, particularly those created without your knowledge or with unusual creation timestampsAffected if Unknown or unauthorized administrator accounts exist in the system
The environment is affected if either the Application version is below 20.0.2253 or the Virtual Appliance Host version is below 22.0.913, or if unauthorized admin accounts are present indicating exploitation.
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
Apply vendor patches by upgrading to Virtual Appliance Host 22.0.913 and Application 20.0.2253 or later. Since this allows unauthorized admin creation, immediately restrict network exposure and audit existing admin accounts.
Vasion Print Application 20.0.2253 / Virtual Appliance Host 22.0.913
- Backup the current Vasion Print configuration before proceeding with the upgrade
- Upgrade Vasion Print Application to version 20.0.2253 or higher
- Upgrade Virtual Appliance Host to version 22.0.913 or higher
- After upgrade, verify that the authentication mechanism is properly enforced for admin user creation
- Confirm that the existing admin users can authenticate successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27647 — 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-27647 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