CVE-2025-27644
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.933 Application 20.0.2368 allows Local Privilege Escalation V-2024-007.
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 (PrinterLogic) Virtual Appliance and Application contain a local privilege escalation vulnerability (V-2024-007) allowing unprivileged users to gain elevated (likely root/administrator) access on the host system. The vulnerability affects versions prior to Virtual Appliance Host 22.0.933 and Application 20.0.2368.
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.2368< 22.0.933CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 installed Vasion Print product typeDetermine whether your environment is running the Virtual Appliance or the Application component of PrinterLogic/Vasion PrintAffected if Either product is present in the environment
-
Check Virtual Appliance versionAccess the Virtual Appliance management interface or use system information commands to retrieve the Host version number. Compare it to the affected range: versions prior to 22.0.933Affected if Virtual Appliance Host version is below 22.0.933
-
Check Application versionAccess the Application administration console or use built-in version reporting to retrieve the Application version number. Compare it to the affected range: versions prior to 20.0.2368Affected if Application version is below 20.0.2368
If either the Virtual Appliance Host version is below 22.0.933 or the Application version is below 20.0.2368, the local privilege escalation vulnerability is present in your environment.
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.236822.0.933
Upgrade Vasion Print Virtual Appliance Host to version 22.0.933 or later and Application to 20.0.2368 or later to remediate this privilege escalation vulnerability.
Vasion Print Application 20.0.2368 or later AND Virtual Appliance Host 22.0.933 or later
- Identify the current version of Vasion Print (formerly PrinterLogic) installed in your environment
- Identify whether you are using Virtual Appliance Host or Application version
- If running Vasion Print Application < 20.0.2368, upgrade to version 20.0.2368 or later
- If running Virtual Appliance Host < 22.0.933, upgrade to version 22.0.933 or later
- After upgrading, verify the new version meets the minimum requirements (Application >= 20.0.2368 and Virtual Appliance Host >= 22.0.933)
- Test the upgrade in a non-production environment first before applying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27644 — 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-27644 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