Skip to main content
CVE-2025-27649VulnerabilityPublished Updated

CVE-2025-27649: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 22.0.893 : patch affected systems as a priority.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 22.0.893, 20.0.2140
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

1. Immediately isolate Vasion Print servers from untrusted networks and restrict access to trusted administrators only using network segmentation and firewall rules. 2. Implement strict access control policies at the network and application layers to limit exposure of the print management interface. 3. Monitor network traffic and system logs for unusual access patterns or unauthorized attempts to interact with the print management system. 4. Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalies related to print management protocols. 5. If you cannot patch yet, consider deploying virtual patching via web application firewalls (WAF) to block suspicious requests targeting known vulnerable endpoints. 6. Conduct an immediate inventory of all Vasion Print instances and verify version numbers to identify affected systems. 7. Develop and test incident response plans specific to print infrastructure compromise scenarios. 8. Educate IT and security teams about this vulnerability and ensure rapid communication channels for updates from Vasion Print vendors. 9. After patches become available, prioritize their deployment in all affected environments, including test and production systems. 10. Review and tighten overall print management policies, including user authentication and authorization mechanisms, to reduce future risk.

Description

Vasion Print (formerly PrinterLogic) before Virtual Appliance Host 22.0.893 Application 20.0.2140 allows Incorrect Access Control: PHP V-2023-016.

References

Community reviews

Loading reviews…