dbcve.org
Vasion PrintApplication · Printerlogic

CVE-2025-27673

CRITICAL · 9.1 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 Cookie Returned in Response Body OVE-20230524-0017.

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 confidence

Vasion Print (formerly PrinterLogic) before the specified versions contains a vulnerability where sensitive cookies are returned in the HTTP response body (OVE-20230524-0017). This exposure could allow an attacker to intercept and steal session cookies, potentially leading to unauthorized access and session hijacking.

MitigationUpgrade Vasion Print Virtual Appliance Host to version 22.0.843 or later and Application to version 20.0.1923 or later to remediate this vulnerability.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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. Identify installed Vasion Print application version
    Log into the PrinterLogic/Vasion Print admin console and navigate to the About or System Information page to view the exact version number. Alternatively, check the application version file on the server if you have direct access.
    Affected if The displayed version is earlier than 20.0.1923 (Application version)
  2. Identify installed Virtual Appliance version
    Access the Virtual Appliance management interface (usually via SSH or the admin panel) and run the command to display the appliance version, or check the system information page.
    Affected if The Virtual Appliance version is earlier than 22.0.843
  3. Verify web interface is accessible
    Confirm that the PrinterLogic/Vasion Print web interface is reachable by accessing the admin URL (typically https://[hostname]/) in a browser or via a curl request.
    Affected if The web interface responds to HTTP/HTTPS requests - this is required for the cookie exposure vulnerability to be exploitable
  4. Inspect HTTP response headers and body for cookie data
    Use browser developer tools (Network tab) or a tool like Burp Suite/curl to capture HTTP responses from the application. Specifically examine response bodies for any cookie values or session tokens that should only appear in Set-Cookie headers.
    Affected if Sensitive cookie values or session identifiers appear in the HTTP response body rather than being restricted to Set-Cookie headers only

You are affected if your installed versions are below 20.0.1923 (Application) or 22.0.843 (Virtual Appliance) AND the web interface is accessible with cookies visible in response bodies.

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

Upgrade Vasion Print Virtual Appliance Host to version 22.0.843 or later and Application to version 20.0.1923 or later to remediate this vulnerability.

Recommended fix High confidence

Virtual Appliance Host 22.0.843 with Application 20.0.1923

  1. Log in to the Vasion Print admin console
  2. Navigate to the Virtual Appliance management section
  3. Verify current version is below 22.0.843 for Virtual Appliance Host or below 20.0.1923 for Application
  4. Initiate the upgrade to Virtual Appliance Host version 22.0.843 and Application version 20.0.1923
  5. Follow the on-screen prompts to complete the upgrade process
  6. Verify the upgrade was successful by checking the version numbers in the admin console
  7. Test that the application functions normally after upgrade

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

Fix this in Vasion Print Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27673 — 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-27673 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