CVE-2025-27664
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 · uneditedVasion Print (formerly PrinterLogic) before Virtual Appliance Host 22.0.843 Application 20.0.1923 allows Insufficient CSRF Protection OVE-20230524-0008.
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 confidenceInsufficient CSRF protection in Vasion Print (formerly PrinterLogic) allows remote attackers to execute unauthorized actions on behalf of authenticated users by tricking them into submitting malicious requests. The vulnerability exists in versions prior to Virtual Appliance Host 22.0.843 and Application 20.0.1923.
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< 20.0.1923< 22.0.843CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Vasion Print product typeDetermine whether your deployment uses the Virtual Appliance Host, the standalone Application, or both. Virtual Appliance is typically a VM-based deployment while Application may run on existing servers.Affected if Running either product type at any version
-
Check Virtual Appliance Host versionLog into the Virtual Appliance admin interface and navigate to System Settings > About, or run the command: sudo plmgr --version or check /etc/version file if accessible via SSHAffected if Version is less than 22.0.843
-
Check Application versionLog into the PrinterLogic/Vasion Print admin console and navigate to Help > About, or check the application version through the installed software properties on the host serverAffected if Version is less than 20.0.1923
-
Verify CSRF protection configurationInspect HTTP responses from the admin interface for the presence of CSRF tokens in forms and API requests. Check if the X-CSRF-Token header is required for state-changing operations.Affected if No CSRF tokens present in requests and no token validation observed in older versions
You are affected if your Virtual Appliance Host version is below 22.0.843 or your Application version is below 20.0.1923, as these versions lack the CSRF protection mechanism.
Generated from the published advisory. Verify against your own configuration.
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 · scoped20.0.192322.0.843
Upgrade to Virtual Appliance Host version 22.0.843 and Application version 20.0.1923 or later, which contain the CSRF protection fixes (OVE-20230524-0008).
Vasion Print 20.0.1923 / Virtual Appliance 22.0.843
- Access the Vasion Print/PrinterLogic admin console
- Navigate to the system update or upgrade section
- Download and install Vasion Print version 20.0.1923 or higher
- If using Virtual Appliance, upgrade to Virtual Appliance version 22.0.843 or higher
- Verify the upgrade was successful by checking the version numbers in the admin panel
- Test critical functionality to ensure the upgrade did not break existing workflows
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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