VulnerabilityPublished 5 Mar 2025Updated 3 Nov 2025

CVE-2025-27684: Vasion Print · Insertion of Sensitive Information Into Debugging Code

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 1.0.735 : patch affected systems soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.735

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Organizations should immediately inventory their print management infrastructure to identify deployments of Vasion Print or PrinterLogic prior to Virtual Appliance Host 1.0.735 Application 20.0.1330. If you cannot patch yet, restrict network access to print management appliances and debug bundle endpoints using firewalls or network segmentation. Disable or tightly control the generation and storage of debug bundles, ensuring they are accessible only to authorized personnel. Implement strict access controls and monitoring on systems that generate or store diagnostic data to detect unauthorized access attempts. Regularly audit logs for suspicious activity related to debug bundle access. Once patches or updates become available from Vasion Print, prioritize their deployment in all affected environments. Additionally, educate IT staff about the risks of exposing debug information and enforce secure development and operational practices to prevent similar issues. Consider deploying network intrusion detection systems to alert on anomalous access patterns to print management systems.

Description

Vasion Print (formerly PrinterLogic) before Virtual Appliance Host 1.0.735 Application 20.0.1330 allows Debug Bundle Contains Sensitive Data V-2022-003.

Impact

For European organizations, the exposure of sensitive data through debug bundles can lead to significant confidentiality breaches, potentially revealing internal network configurations, user credentials, or other proprietary information. This can facilitate lateral movement by attackers, targeted phishing, or further exploitation of internal systems. Sectors such as government, finance, healthcare, and manufacturing, which often rely on centralized print management solutions like Vasion Print, are particularly vulnerable. The impact is heightened in environments where print servers are connected to critical infrastructure or contain sensitive documents. Although the vulnerability does not directly affect system integrity or availability, the confidentiality breach alone can result in regulatory penalties under GDPR and damage to organizational reputation. The lack of required privileges or user interaction lowers the barrier for exploitation, increasing the risk of widespread unauthorized data access if the vulnerability is not promptly addressed.

CWE-215Insertion of Sensitive Information Into Debugging Code (opens in a new tab)
Base weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.
Implementation
Do not leave debug statements that could be executed in the source code. Ensure that all debug information is eradicated before releasing the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2025, 21:06 UTC

WeaknessesCWE-215

Technical details

References

Community reviews

Related threats