dbcve.org
Vasion PrintApplication · Printerlogic

CVE-2025-27667

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 Administrative User Email Enumeration OVE-20230524-0011.

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 (formerly PrinterLogic) contains an administrative user email enumeration vulnerability (OVE-20230524-0011) that allows attackers to discover valid admin email addresses through the application. This information disclosure flaw enables attackers to gather valid usernames for subsequent attacks such as password guessing or phishing campaigns.

MitigationUpgrade to Virtual Appliance Host version 22.0.843 or Application version 20.0.1923 or later. Additionally, implement rate limiting, account lockout policies, and CAPTCHA on login/forgot-password endpoints to prevent automated enumeration.

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. Identify the PrinterLogic/Vasion Print version
    Access the admin web interface and navigate to Help > About, or check the login page footer for version information. On the Virtual Appliance, you can also SSH in and run: cat /etc/lsb-release or check the admin panel dashboard for the build number.
    Affected if The displayed version number is less than 20.0.1923 for Vasion Print application or less than 22.0.843 for Virtual Appliance.
  2. Confirm the product deployment type
    Determine whether you are running the Vasion Print application (installed on Windows/Linux server) or the Virtual Appliance (VMware/Hyper-V OVA). The version number format differs between these deployments.
    Affected if You are running either product type and the version falls below the corresponding threshold.
  3. Verify the web interface is accessible
    Attempt to access the login page of the PrinterLogic/Vasion Print admin console via browser at your configured URL (e.g., https://your-server/PrinterLogic). Confirm the page loads successfully.
    Affected if The web interface is accessible and the version check in Step 1 shows an affected version.
  4. Inspect response behavior on password reset
    In a controlled test, submit the password reset functionality with a known admin email address and observe the response message. Compare with a non-existent email to check if the application reveals account existence.
    Affected if The application returns different messages or response times for valid versus invalid email addresses, indicating enumeration is possible.

Your environment is affected if you are running PrinterLogic Vasion Print below version 20.0.1923 or Virtual Appliance below version 22.0.843 and the web admin interface is accessible.

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 to Virtual Appliance Host version 22.0.843 or Application version 20.0.1923 or later. Additionally, implement rate limiting, account lockout policies, and CAPTCHA on login/forgot-password endpoints to prevent automated enumeration.

Recommended fix Moderate confidence

Virtual Appliance Host 22.0.843 with Application 20.0.1923 or later

  1. 1. Identify current Vasion Print Application version in the admin console or system information
  2. 2. Identify current Virtual Appliance Host version in the admin console or system information
  3. 3. Download the upgrade package for Virtual Appliance Host 22.0.843 or later with Application 20.0.1923 or later from help.printerlogic.com or your Vasion customer portal
  4. 4. Follow Vasion's documented upgrade procedure to apply the update
  5. 5. After upgrade, verify the version numbers reflect 20.0.1923 (Application) and 22.0.843 (Virtual Appliance Host) or higher
  6. 6. Confirm the email enumeration vulnerability is resolved by attempting the previously exploitable endpoint

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 / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

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