# CVE-2025-34232: Vasion Print (formerly PrinterLogic) Blind SSRF via Lexmark dellCheck.php

> Unauthenticated attackers can exploit a blind SSRF vulnerability in Vasion Print to probe internal services and gather intelligence via the Lexmark check script.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-h4fj-xhpc-c3pm

## What is CVE-2025-34232?

CVE-2025-34232 is a medium-severity server-side request forgery vulnerability in Vasion Print Application, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 25.1.102 and Application prior to version 25.1.1413 (VA/SaaS deployments) contain a blind server-side request forgery (SSRF) vulnerability reachable via the /var/www/app/console_release/lexmark/dellCheck.php script that can be exploited by an unauthenticated user. When a printer is registered, the software stores the printer’s host name in the variable $printer_vo->str_host_address. The code later builds a URL like 'http://<host‑address>:80/DevMgmt/DiscoveryTree.xml' and sends the request with curl. No validation, whitelist, or private‑network filtering is performed before the request is made. Because the request is blind, an attacker cannot see the data directly, but can still: probe internal services, trigger internal actions, or gather other intelligence. This vulnerability has been confirmed to be remediated, but it is unclear as to when the patch was introduced.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-34232?

It affects 2 products.


Products: Vasion Virtual Appliance Application, Vasion Virtual Appliance Host.

## How do I fix CVE-2025-34232?

No fix has been published for CVE-2025-34232 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-34232 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34232 exists.

## Other vulnerabilities in Vasion Print Application

- [CVE-2025-34217](https://insights.sbomify.com/CVE-2025-34217/): Vasion Print (formerly PrinterLogic) Undocumented Hardcoded SSH Key (critical 10.0)
- [CVE-2025-34216](https://insights.sbomify.com/CVE-2025-34216/): Vasion Print (formerly PrinterLogic) RCE and Password Leaks via API (critical 10.0)
- [CVE-2025-34218](https://insights.sbomify.com/CVE-2025-34218/): Vasion Print (formerly PrinterLogic) Exposed Internal Docker Instance (critical 10.0)
- [CVE-2025-34221](https://insights.sbomify.com/CVE-2025-34221/): Vasion Print (formerly PrinterLogic) (critical 10.0)
- [CVE-2025-34222](https://insights.sbomify.com/CVE-2025-34222/): Vasion Print (formerly PrinterLogic) Unauthenticated Admin APIs Used to Modify SSL Certificates (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34232 and fix it if it is affected.

What it is: CVE-2025-34232 is a medium-severity server-side request forgery vulnerability in Vasion Print Application, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34232 exists.

Affected product: Vasion Print Application. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34232/ (Markdown: https://insights.sbomify.com/CVE-2025-34232/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34232
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34232
- OSV: https://osv.dev/vulnerability/CVE-2025-34232

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34232/
Summaries are generated and may contain mistakes; the official description above is the record.