CVE-2025-27641
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.951 Application 20.0.2368 allows Unauthenticated APIs for Single-Sign On V-2024-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 confidenceVasion Print (formerly PrinterLogic) contains an authentication bypass vulnerability in its Single Sign-On (SSO) functionality. The vulnerability allows unauthenticated attackers to access sensitive SSO-related APIs, potentially leading to unauthorized access to the platform and its resources. The flaw exists in versions prior to Virtual Appliance Host 22.0.951 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.951CVSS 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 installed Vasion Print/PrinterLogic product versionAccess the admin console or check the applicationAbout page. In the admin panel, navigate to System Settings or About to find the Application version number.Affected if The Application version is below 20.0.2368
-
Identify the Virtual Appliance Host versionAccess the appliance management interface or check the host system information. Look for the Virtual Appliance version in the system administration or status page.Affected if The Virtual Appliance Host version is below 22.0.951
-
Verify if Single Sign-On (SSO) is configured and enabledIn the admin console, navigate to Settings > Authentication or Single Sign-On configuration. Check if any SSO provider (such as SAML, OAuth, or LDAP) is actively configured.Affected if SSO is enabled and the version checks in steps 1 or 2 indicate vulnerable releases
-
Inspect SSO API endpoint accessibilityFrom an unauthenticated network perspective, attempt to access common SSO-related API endpoints such as /sso/api, /api/sso, or /saml endpoints. Use a web request tool to check for unexpected HTTP response codes indicating access.Affected if SSO API endpoints return successful authentication responses without credentials
-
Review SSO-related audit logs for unauthorized accessExamine the Vasion Print audit logs focusing on SSO authentication events. Look for successful authentications from IP addresses or users that are not recognized or expected.Affected if There are SSO authentication events from unrecognized sources or unusual patterns
A defender is affected if they are running any version of Vasion Print/PrinterLogic with an Application version below 20.0.2368 or a Virtual Appliance Host version below 22.0.951, and have SSO functionality 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.236822.0.951
Upgrade to Virtual Appliance Host version 22.0.951 and Application version 20.0.2368 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to SSO endpoints and monitor for unauthorized access attempts.
Vasion Print Application 20.0.2368+ and Virtual Appliance Host 22.0.951+
- 1. Identify current Vasion Print Application version and Virtual Appliance Host version from the admin console or system information
- 2. Download the latest Vasion Print installer from help.printerlogic.com or your designated update channel
- 3. If running Virtual Appliance, upgrade Virtual Appliance Host to version 22.0.951 or later first (this is the host platform)
- 4. Upgrade Vasion Print Application to version 20.0.2368 or later
- 5. After upgrade, verify the Single Sign-On configuration is intact and functional
- 6. Confirm unauthenticated API endpoints are no longer accessible by testing SSO authentication flow
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27641 — 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-27641 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