CVE-2025-60641: n/a
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.
AI Analysis
Technical Summary
The vulnerability in Vfront 0.99.52 arises from the use of unserialize(base64_decode($_POST['mexcel'])) in mexcel.php without validating or restricting the classes allowed during deserialization. Since the input is user-controlled, an attacker can craft serialized PHP objects to trigger unintended behaviors. This can lead to various impacts including remote code execution, SQL injection, path traversal, or denial of service, contingent on the availability of exploitable classes in Vfront or its dependencies. The CVSS score of 6.5 reflects a medium severity with network attack vector, low attack complexity, no privileges or user interaction required, and partial confidentiality and integrity impact.
Potential Impact
The vulnerability allows remote attackers to inject arbitrary PHP objects via unsafe deserialization of user-supplied input, potentially resulting in remote code execution, SQL injection, path traversal, or denial of service. The actual impact depends on the presence of exploitable classes in the affected application or its dependencies. Confidentiality and integrity impacts are rated low, with no impact on availability according to the CVSS vector.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, it is recommended to avoid exposing the vulnerable endpoint or disable the mexcel.php functionality if possible. Applying input validation, restricting allowed classes during unserialization, or replacing unsafe unserialize calls with safer alternatives are potential mitigations. Monitor vendor channels for updates and patches.
CVE-2025-60641: n/a
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.
CVSS v3.1
Score 6.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Vfront 0.99.52 arises from the use of unserialize(base64_decode($_POST['mexcel'])) in mexcel.php without validating or restricting the classes allowed during deserialization. Since the input is user-controlled, an attacker can craft serialized PHP objects to trigger unintended behaviors. This can lead to various impacts including remote code execution, SQL injection, path traversal, or denial of service, contingent on the availability of exploitable classes in Vfront or its dependencies. The CVSS score of 6.5 reflects a medium severity with network attack vector, low attack complexity, no privileges or user interaction required, and partial confidentiality and integrity impact.
Potential Impact
The vulnerability allows remote attackers to inject arbitrary PHP objects via unsafe deserialization of user-supplied input, potentially resulting in remote code execution, SQL injection, path traversal, or denial of service. The actual impact depends on the presence of exploitable classes in the affected application or its dependencies. Confidentiality and integrity impacts are rated low, with no impact on availability according to the CVSS vector.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, it is recommended to avoid exposing the vulnerable endpoint or disable the mexcel.php functionality if possible. Applying input validation, restricting allowed classes during unserialization, or replacing unsafe unserialize calls with safer alternatives are potential mitigations. Monitor vendor channels for updates and patches.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- mitre
- Date Reserved
- 2025-09-26T00:00:00.000Z
- State
- PUBLISHED
Threat ID: 68f132679f8a5dbaeaef9b8f
Added to database: 10/16/2025, 17:59:03 UTC
Last enriched: 07/05/2026, 21:32:21 UTC
Last updated: 09/10/2026, 19:24:57 UTC
Views: 251
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.