CVE-2025-27672
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.843 Application 20.0.1923 allows OAUTH Security Bypass OVE-20230524-0016.
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 OAuth security bypass vulnerability (OVE-20230524-0016) that allows attackers to circumvent authentication mechanisms. The vulnerability affects versions prior to Virtual Appliance Host 22.0.843 and Application 20.0.1923, enabling unauthorized access to the platform.
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.1923< 22.0.843CVSS 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 versionAccess the PrinterLogic/Vasion Print admin console and navigate to Help > About, or check the application version file in the installation directory if accessible via SSHAffected if The displayed version is earlier than 20.0.1923 (e.g., 20.0.x where x < 1923, or any version below 20.0)
-
Check Virtual Appliance Host versionAccess the Vasion Print Virtual Appliance admin panel or log in via SSH and run: cat /etc/version or check the appliance management interface for the build numberAffected if The Virtual Appliance version is earlier than 22.0.843 (e.g., 22.0.x where x < 843, or any version below 22.0)
-
Verify OAuth authentication is in useIn the admin console, go to Settings > Authentication or Security settings and confirm that OAuth/OAuth2 is enabled as the authentication methodAffected if OAuth-based authentication is configured and the version checks in steps 1 or 2 show vulnerable releases
You are affected if either the Application version is below 20.0.1923 or the Virtual Appliance Host version is below 22.0.843, particularly when OAuth authentication is enabled.
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.192322.0.843
Immediately upgrade Vasion Print to Virtual Appliance Host 22.0.843 or higher and Application 20.0.1923 or higher to remediate this critical OAuth bypass vulnerability.
Vasion Print 20.0.1923 or Virtual Appliance 22.0.843 (or later versions)
- Identify the current installed version of Vasion Print or Virtual Appliance
- For Vasion Print: Upgrade to version 20.0.1923 or later
- For Virtual Appliance: Upgrade to version 22.0.843 or later
- Verify the upgrade was successful and the version is now at or above the fixed release
- Test that OAuth authentication is functioning properly after upgrade
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-27672 — 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-27672 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