dbcve.org
Virtual Appliance ApplicationApplication · Vasion

CVE-2025-34216

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 20.0.2702 / 22.0.1026 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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) Virtual Appliance Host prior to version 22.0.1026 and Application prior to version 20.0.2702 (VA deployments only) expose a set of unauthenticated REST API endpoints that return configuration files and clear‑text passwords. The same endpoints also disclose the Laravel APP_KEY used for cryptographic signing. Because the APP_KEY is required to generate valid signed requests, an attacker who obtains it can craft malicious payloads that are accepted by the application and achieve remote code execution on the appliance. This vulnerability has been identified by the vendor as: V-2024-018 — RCE & Leaks via API.

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 Virtual Appliance exposes unauthenticated REST API endpoints that leak configuration files, clear-text passwords, and the Laravel APP_KEY. The exposed APP_KEY allows attackers to forge valid signed requests, enabling remote code execution on the appliance.

MitigationUpgrade Vasion Print Virtual Appliance Host to version 22.0.1026 or Application to version 20.0.2702 (or later) to patch the vulnerable unauthenticated API endpoints.

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
Virtual Appliance ApplicationApplication
Affected:< 20.0.2702
Virtual Appliance HostApplication
Affected:< 22.0.1026

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. Check Vasion Virtual Appliance Application version
    Access the appliance admin interface or check /opt/vasion/version file (or similar version file in the installation directory) to determine the installed Application version
    Affected if Version is below 20.0.2702 (e.g., 20.0.x where x < 2702, or any earlier major version)
  2. Check Vasion Virtual Appliance Host version
    Access the appliance hypervisor console or check the host system package version (e.g., via 'rpm -q vasion-host' or 'dpkg -l vasion-host' depending on OS) to determine the Host version
    Affected if Version is below 22.0.1026 (e.g., 22.0.x where x < 1026, or any earlier major version)
  3. Test unauthenticated API endpoint accessibility
    From an external host, attempt HTTP GET requests to common Vasion REST API paths such as /api/v1/config, /api/config, /api/settings, or /api/v1/settings without providing any authentication credentials
    Affected if The endpoints respond with HTTP 200 OK and return JSON data containing configuration files, passwords, or APP_KEY without requiring authentication
  4. Inspect response for exposed APP_KEY
    If the API endpoints respond, examine the JSON body for a field named 'APP_KEY', 'app_key', or 'key' containing a base64-encoded 32-byte value (typically 64 characters)
    Affected if The API response contains a valid Laravel APP_KEY value that could be used to forge signed requests
  5. Verify clear-text password exposure
    Search the API response for password fields (e.g., 'password', 'db_password', 'smtp_password') that contain readable plain-text passwords rather than hashed or masked values
    Affected if The API responses expose passwords in plain text that should not be accessible without authentication

You are affected if either your Vasion Virtual Appliance Application version is below 20.0.2702 or your Host version is below 22.0.1026, AND the unauthenticated API endpoints are accessible and leaking the APP_KEY or other sensitive configuration data.

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.2702 / 22.0.1026 or later
Fixed in 20.0.270222.0.1026
Interim mitigation

Upgrade Vasion Print Virtual Appliance Host to version 22.0.1026 or Application to version 20.0.2702 (or later) to patch the vulnerable unauthenticated API endpoints.

Recommended fix High confidence

Virtual Appliance Application: 20.0.2702 | Virtual Appliance Host: 22.0.1026

  1. Identify the current version of the Virtual Appliance Application and Virtual Appliance Host installations
  2. Upgrade Virtual Appliance Application to version 20.0.2702 or later
  3. Upgrade Virtual Appliance Host to version 22.0.1026 or later
  4. After upgrade, verify the REST API endpoints now require authentication and that the APP_KEY is no longer exposed

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

Fix this in Virtual Appliance Application 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-34216 — 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-34216 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