dbcve.org
Vasion PrintApplication · Printerlogic

CVE-2025-27674

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to 20.0.1923 / 22.0.843 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Vasion Print (formerly PrinterLogic) before Virtual Appliance Host 22.0.843 Application 20.0.1923 allows Hardcoded IdP Key V-2023-006.

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 confidence

Vasion Print (PrinterLogic) contains a hardcoded Identity Provider (IdP) cryptographic key in versions prior to Virtual Appliance Host 22.0.843 and Application 20.0.1923. This hardcoded key (V-2023-006) cannot be rotated or changed by administrators, potentially allowing attackers to impersonate the IdP or bypass authentication mechanisms.

MitigationUpdate Vasion Print to Virtual Appliance Host 22.0.843 / Application 20.0.1923 or later to remove the hardcoded IdP key. After updating, verify IdP configuration and consider rotating any authentication tokens that may have been compromised.

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
Vasion PrintApplication
Affected:< 20.0.1923
Virtual ApplianceApplication
Affected:< 22.0.843

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Vasion Print application version
    Access the PrinterLogic/Vasion Print admin console and navigate to the About or System Information section to view the current version number. Alternatively, check the application's installer or the software inventory on the host system.
    Affected if The installed version is below 20.0.1923 for the Application component or below 22.0.843 for the Virtual Appliance Host component.
  2. Identify if IdP/SAML authentication is configured
    Log into the PrinterLogic admin panel and navigate to Settings > Identity Provider or Settings > SSO/SAML Configuration. Verify whether an external Identity Provider has been configured and is currently enabled.
    Affected if An external IdP or SAML single sign-on is configured and active, as this is the feature that relies on the hardcoded cryptographic key.
  3. Review IdP configuration for hardcoded credentials
    Examine the IdP configuration files or XML metadata stored on the Virtual Appliance. Look for embedded cryptographic keys, certificates, or secrets that appear static rather than generated per-deployment.
    Affected if A static, unchanging cryptographic key or secret is found embedded in the IdP configuration or application files.
  4. Check authentication logs for token anomalies
    Review PrinterLogic authentication and audit logs for patterns such as successful logins from unexpected IP ranges, unusual token claims, or authentication attempts using the same token multiple times across different sessions.
    Affected if Authentication logs show suspicious patterns indicative of token forgery or reuse that suggests the hardcoded key may have been exploited.

A user is affected if their installed version is below 20.0.1923 (Application) or 22.0.843 (Virtual Appliance) AND they have an IdP/SAML authentication configured, as this combination exposes the environment to token forgery via the hardcoded key.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 20.0.1923 / 22.0.843 or later
Fixed in 20.0.192322.0.843
Interim mitigation

Update Vasion Print to Virtual Appliance Host 22.0.843 / Application 20.0.1923 or later to remove the hardcoded IdP key. After updating, verify IdP configuration and consider rotating any authentication tokens that may have been compromised.

Recommended fix High confidence

Virtual Appliance Host 22.0.843 / Application 20.0.1923

  1. Determine the current version of Vasion Print (PrinterLogic) and the Virtual Appliance Host.
  2. Back up the current configuration and any custom IdP settings.
  3. Download the latest Vasion Print installer and Virtual Appliance Host update from the vendor (e.g., help.printerlogic.com).
  4. Upgrade the Virtual Appliance Host to version 22.0.843 or later.
  5. Upgrade the Vasion Print application to version 20.0.1923 or later.
  6. After upgrade, log in and reconfigure the IdP/SSO with a new, securely generated key to replace the removed hardcoded key.
  7. Verify that the hardcoded IdP key is no longer present and that single sign-on works correctly.
Caveat The IdP/SSO configuration must be updated after upgrade because the hardcoded key has been removed.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vasion Print Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27674 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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