CVE-2025-26378

8.8 HIGH

📋 TL;DR

A missing authorization vulnerability in Q-Free MaxTime allows authenticated low-privileged users to reset passwords, including administrator accounts, via crafted HTTP requests. This affects all installations running version 2.11.0 or earlier. Attackers with basic user access can escalate privileges to administrative control.

💻 Affected Systems

Products:
  • Q-Free MaxTime
Versions: <= 2.11.0
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: All installations with default configurations are vulnerable. The vulnerability exists in the maxprofile/users/routes.lua file.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise where attackers gain administrative access, modify configurations, access sensitive data, and potentially disrupt operations.

🟠

Likely Case

Privilege escalation leading to unauthorized administrative access, data exposure, and potential lateral movement within the network.

🟢

If Mitigated

Limited impact with proper network segmentation, strong authentication controls, and monitoring in place to detect unusual password reset activities.

🌐 Internet-Facing: HIGH - If MaxTime is exposed to the internet, attackers can exploit this after obtaining any user credentials.
🏢 Internal Only: HIGH - Even internally, any compromised low-privileged account can lead to administrative takeover.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires authenticated access but only low privileges. Crafting HTTP requests to the vulnerable endpoint is straightforward for attackers with basic web skills.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version > 2.11.0

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

Restart Required: No

Instructions:

1. Contact Q-Free for the latest patched version. 2. Backup current configuration. 3. Apply the update following vendor instructions. 4. Verify authorization checks are properly implemented.

🔧 Temporary Workarounds

Network Access Control

all

Restrict access to MaxTime administration interfaces to trusted IP addresses only.

Use firewall rules to limit access to MaxTime ports (e.g., iptables -A INPUT -p tcp --dport [PORT] -s [TRUSTED_IP] -j ACCEPT)

Enhanced Monitoring

all

Monitor for unusual password reset activities, especially for administrator accounts.

Configure log alerts for POST requests to password reset endpoints from non-admin users

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate MaxTime from other critical systems
  • Enforce multi-factor authentication for all user accounts to reduce impact of credential compromise

🔍 How to Verify

Check if Vulnerable:

Check MaxTime version via web interface or configuration files. If version <= 2.11.0, system is vulnerable.

Check Version:

Check web interface or configuration files for version information. No single command available for all deployments.

Verify Fix Applied:

After patching, test that low-privileged users cannot reset administrator passwords via HTTP requests.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to password reset endpoints from low-privileged users
  • Multiple failed login attempts followed by password reset requests
  • Administrator password reset events from non-admin IP addresses

Network Indicators:

  • HTTP requests to /maxprofile/users/reset-password or similar endpoints with unusual parameters
  • Traffic patterns showing privilege escalation attempts

SIEM Query:

source="maxtime_logs" AND (uri_path="/reset-password" OR uri_path="/password/reset") AND user_role!="admin" AND status=200

🔗 References

📤 Share & Export