dbcve.org
Vasion PrintApplication · Printerlogic

CVE-2025-27653

MEDIUM · 6.1 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to 20.0.2014 / 22.0.862 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.862 Application 20.0.2014 allows Preauthenticated Cross Site Scripting (XSS): Badge Registration V-2023-012.

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) contains a pre-authenticated Cross Site Scripting (XSS) vulnerability in the Badge Registration functionality. An unauthenticated attacker can inject malicious JavaScript code through the Badge Registration endpoint (V-2023-012), which executes in the browsers of users who access the affected page, potentially leading to session hijacking or credential theft.

MitigationUpgrade Vasion Print Virtual Appliance Host to version 22.0.862 or later and Application to version 20.0.2014 or later to obtain the patched version. As a temporary mitigation, restrict external access to the Badge Registration endpoint using network-level controls or a WAF.

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.2014
Virtual ApplianceApplication
Affected:< 22.0.862

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 version
    Log into the Vasion Print admin console and navigate to Help > About, or check the version displayed on the login page. For Virtual Appliance, check the appliance management interface for the version number.
    Affected if The installed version is below 20.0.2014 for the application or below 22.0.862 for the Virtual Appliance.
  2. Confirm Badge Registration feature is enabled
    Access the Vasion Print admin panel and navigate to the Badge Registration settings (typically under Admin > Badge Registration or System Settings > Badge Settings). Verify if the feature is toggled to enabled.
    Affected if The Badge Registration feature is enabled in the Vasion Print configuration.
  3. Check Badge Registration endpoint accessibility
    Attempt to access the Badge Registration endpoint directly via browser or curl: /admin/badge-registration or the V-2023-012 endpoint path. Determine if the page loads without authentication.
    Affected if The Badge Registration endpoint loads without requiring authentication.
  4. Verify XSS vulnerability exists
    Submit a benign XSS test payload (such as <script>alert(1)</script>) through the Badge Registration form fields. If the payload executes or is reflected unescaped in the response, the vulnerability is present.
    Affected if The submitted payload is reflected in the page source without proper encoding or sanitization, indicating the XSS vulnerability is present.

Your environment is affected if you are running Vasion Print version below 20.0.2014 (application) or 22.0.862 (Virtual Appliance) AND the Badge Registration feature is enabled and 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.2014 / 22.0.862 or later
Fixed in 20.0.201422.0.862
Interim mitigation

Upgrade Vasion Print Virtual Appliance Host to version 22.0.862 or later and Application to version 20.0.2014 or later to obtain the patched version. As a temporary mitigation, restrict external access to the Badge Registration endpoint using network-level controls or a WAF.

Recommended fix High confidence

Vasion Print Application 20.0.2014 / Virtual Appliance Host 22.0.862

  1. Back up the current Vasion Print configuration and database
  2. Download Vasion Print Application version 20.0.2014 or later
  3. Download Virtual Appliance Host version 22.0.862 or later
  4. Upgrade the Virtual Appliance Host to version 22.0.862
  5. Upgrade the Vasion Print Application to version 20.0.2014
  6. Log in to the admin console and verify the Badge Registration functionality works correctly
  7. Confirm the XSS vulnerability is no longer present by testing Badge Registration input fields
Caveat Review Vasion Print release notes for any breaking changes between your current version and 20.0.2014

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
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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