# CVE-2025-60641: Deserialization in n/a

> Attackers can achieve remote code execution and other impacts by sending malicious serialized data to the mexcel.php endpoint in Vfront.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-mq92-56vj-hj5v

## What is CVE-2025-60641?

CVE-2025-60641 is a medium-severity unsafe deserialization vulnerability in n/a, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The file mexcel.php in the Vfront 0.99.52 codebase contains a vulnerable call to unserialize(base64_decode($_POST['mexcel'])), where $_POST['mexcel'] is user-controlled input. This input is decoded from base64 and deserialized without validation or use of the allowed_classes option, allowing an attacker to inject arbitrary PHP objects. This can lead to malicious behavior, such as Remote Code Execution (RCE), SQL Injection, Path Traversal, or Denial of Service, depending on the availability of exploitable classes in the Vfront codebase or its dependencies.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2025-60641 being exploited?

There is no known exploitation of CVE-2025-60641 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60641 is a medium-severity unsafe deserialization vulnerability in n/a, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-60641 in the wild and no public exploit code.

Affected product: n/a. 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-60641/ (Markdown: https://insights.sbomify.com/CVE-2025-60641/index.md)
```

## Sources

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

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