Goal Reached Thanks to every supporter โ€” we hit 100%!

Goal: 1000 CNY ยท Raised: 1336 CNY

100%

CVE-2025-26361 โ€” AI Deep Analysis Summary

CVSS 9.1 ยท Critical

Q1What is this vulnerability? (Essence + Consequences)

๐Ÿšจ **Essence**: Critical Access Control Error in Q-Free MAXTIME Suite. <br>๐Ÿ’ฅ **Consequences**: Attackers can trigger a **factory reset** via crafted HTTP requests, causing total service disruption and data loss.

Q2Root Cause? (CWE/Flaw)

๐Ÿ›ก๏ธ **Root Cause**: **CWE-306** (Missing Authentication for Critical Function). <br>๐Ÿ” **Flaw**: The `maxprofile/setup/routes.lua` script lacks identity verification, allowing unauthorized execution.

Q3Who is affected? (Versions/Components)

๐Ÿข **Vendor**: Q-Free. <br>๐Ÿ“ฆ **Product**: MaxTime (Local Traffic Signal Management). <br>๐Ÿ“… **Affected**: Versions **2.11.0 and earlier**.

Q4What can hackers do? (Privileges/Data)

๐Ÿ•ต๏ธ **Attacker Action**: Send specific HTTP requests to execute the reset function. <br>๐Ÿ“‰ **Impact**: **High Integrity (I:H)** & **High Availability (A:H)** impact.โ€ฆ

Q5Is exploitation threshold high? (Auth/Config)

โšก **Threshold**: **LOW**. <br>๐Ÿ”“ **Auth**: **None required** (PR:N). <br>๐ŸŒ **Access**: Network accessible (AV:N). <br>๐Ÿ‘ค **User Interaction**: None needed (UI:N). Easy to exploit remotely.

Q6Is there a public Exp? (PoC/Wild Exploitation)

๐Ÿ“œ **Public Exploit**: **No PoC provided** in the data. <br>๐ŸŒ **Wild Exploitation**: Unknown status. However, the low barrier to entry makes it highly likely to be weaponized soon.

Q7How to self-check? (Features/Scanning)

๐Ÿ” **Self-Check**: Scan for Q-Free MAXTIME Suite services. <br>๐Ÿงช **Test**: Attempt to access `maxprofile/setup/routes.lua` endpoints. If no auth is prompted and the endpoint is reachable, you are vulnerable.

Q8Is it fixed officially? (Patch/Mitigation)

๐Ÿฉน **Official Fix**: **Yes**. The advisory implies a fix exists for versions newer than 2.11.0. <br>โœ… **Action**: Upgrade to the latest patched version immediately.

Q9What if no patch? (Workaround)

๐Ÿšง **No Patch Workaround**: <br>1. **Network Segmentation**: Block external access to the management interface. <br>2. **WAF Rules**: Filter HTTP requests targeting `routes.lua`. <br>3.โ€ฆ

Q10Is it urgent? (Priority Suggestion)

๐Ÿ”ฅ **Urgency**: **CRITICAL**. <br>โฑ๏ธ **Priority**: **P1**. <br>๐Ÿ’ก **Reason**: Remote, unauthenticated, high impact (DoS/Data Loss). Immediate patching or mitigation is required to protect traffic infrastructure.