# CVE-2025-5100: KL-001-2025-005: Mobile Dynamix PrinterShare Mobile Print Double-Free Memory Write

> A double-free vulnerability in PrinterShare Mobile Print allows attackers to corrupt memory and potentially execute arbitrary code.

- **Severity:** High 8.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2025
- **Updated:** 27 May 2025
- **Also known as:** GHSA-cvx2-phg2-qp2h

## What is CVE-2025-5100?

CVE-2025-5100 is a high-severity use after free vulnerability in PrinterShare Mobile Print, published on 23 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A double-free condition occurs during the cleanup of temporary image files, which can be exploited to achieve memory corruption and potentially arbitrary code execution.

Weakness: CWE-416 (Use After Free), CWE-415 (Double Free)

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

It affects 1 product.


Products: Dynamixsoftware Printershare.

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

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

## Is CVE-2025-5100 being exploited?

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

## Other vulnerabilities in PrinterShare Mobile Print

- [CVE-2025-5099](https://insights.sbomify.com/CVE-2025-5099/): KL-001-2025-004: Mobile Dynamix PrinterShare Mobile Print Out-of-bounds Write (critical 9.8)
- [CVE-2025-5098](https://insights.sbomify.com/CVE-2025-5098/): KL-001-2025-003: Mobile Dynamix PrinterShare Mobile Print Gmail Oauth Token Disclosure (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5100 is a high-severity use after free vulnerability in PrinterShare Mobile Print, published on 23 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5100 exists.

Affected product: PrinterShare Mobile Print. 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-5100/ (Markdown: https://insights.sbomify.com/CVE-2025-5100/index.md)
```

## Sources

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

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