CVE-2025-26341

9.8 CRITICAL

📋 TL;DR

This vulnerability allows unauthenticated remote attackers to reset arbitrary user passwords in Q-Free MaxTime systems via crafted HTTP requests. It affects all installations running version 2.11.0 or earlier. Attackers can gain unauthorized access to user accounts without any authentication.

💻 Affected Systems

Products:
  • Q-Free MaxTime
Versions: Versions ≤ 2.11.0
Operating Systems: Any OS running MaxTime
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations of affected versions are vulnerable. The vulnerability is in the maxprofile/accounts/routes.lua file.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise where attackers reset all user passwords, take over administrative accounts, and gain full control over the MaxTime system and connected infrastructure.

🟠

Likely Case

Attackers reset passwords for multiple user accounts, gaining unauthorized access to sensitive data, manipulating time/attendance records, and potentially escalating privileges.

🟢

If Mitigated

Limited impact with proper network segmentation and authentication controls, but still exposes the vulnerable endpoint to internal threats.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable without authentication, making internet-facing instances extremely vulnerable to attack.
🏢 Internal Only: HIGH - Even internally, unauthenticated attackers on the network can exploit this vulnerability to compromise user accounts.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability requires only crafted HTTP requests to the vulnerable endpoint, making exploitation straightforward for attackers with network access.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version > 2.11.0

Vendor Advisory: https://www.nozominetworks.com/labs/vulnerability-advisories-cve-2025-26341

Restart Required: Yes

Instructions:

1. Contact Q-Free for updated version >2.11.0. 2. Backup current configuration. 3. Apply the patch/upgrade. 4. Restart MaxTime services. 5. Verify functionality.

🔧 Temporary Workarounds

Network Access Control

linux

Restrict network access to MaxTime web interface to trusted IPs only

iptables -A INPUT -p tcp --dport [MaxTime_port] -s [trusted_IP] -j ACCEPT
iptables -A INPUT -p tcp --dport [MaxTime_port] -j DROP

Web Server Authentication

all

Implement basic authentication at web server level for the vulnerable endpoint

# Add to Apache .htaccess: AuthType Basic
# AuthName "Restricted Area"
# AuthUserFile /path/to/.htpasswd
# Require valid-user

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate MaxTime from untrusted networks
  • Deploy a WAF with rules to block unauthorized password reset requests

🔍 How to Verify

Check if Vulnerable:

Check if MaxTime version is ≤2.11.0 and test if unauthenticated password reset requests to /maxprofile/accounts/ routes succeed

Check Version:

Check MaxTime web interface admin panel or configuration files for version information

Verify Fix Applied:

Verify version is >2.11.0 and test that unauthenticated password reset requests now fail with proper authentication errors

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed authentication attempts followed by successful password reset
  • Password reset requests from unusual IP addresses
  • POST requests to /maxprofile/accounts/reset without authentication

Network Indicators:

  • Unusual HTTP traffic patterns to password reset endpoints
  • Multiple password reset requests from single source in short time

SIEM Query:

source="MaxTime" AND (uri_path="/maxprofile/accounts/reset" OR uri_path="/maxprofile/accounts/*") AND http_method="POST" AND NOT auth_success="true"

🔗 References

📤 Share & Export