CVE-2025-26366
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA CWE-306 "Missing Authentication for Critical Function" in maxprofile/setup/routes.lua in Q-Free MaxTime less than or equal to version 2.11.0 allows an unauthenticated remote attacker to disable front panel authentication via crafted HTTP requests.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe setup routes in Q-Free MaxTime (maxprofile/setup/routes.lua) versions 2.11.0 and prior lack authentication checks, allowing unauthenticated remote attackers to send crafted HTTP requests that disable front panel authentication. This effectively removes security controls for accessing the device interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Q-Free MaxTime is installedLocate the MaxTime installation directory or check for the maxprofile component on the system. Common locations may include C:\Program Files\Q-Free\MaxTime or /opt/maxtime. Look for the maxprofile folder and the setup subdirectory.Affected if The maxprofile/setup/routes.lua file exists on the system, indicating MaxTime is present.
-
Determine the installed MaxTime versionLocate the version information file within the MaxTime installation. This may be in an about dialog, version.txt, or the main executable metadata. Compare the found version to 2.11.0.Affected if The installed version is 2.11.0 or any version prior to 2.11.0.
-
Verify the vulnerable routes.lua file existsCheck for the presence of the file maxprofile/setup/routes.lua in the MaxTime installation directory.Affected if The file maxprofile/setup/routes.lua exists in the installation directory.
-
Check web interface accessibilityAttempt to access the MaxTime web interface setup routes from an unauthorized network perspective. If the device web interface is exposed to untrusted networks, attempt to reach the setup endpoints (such as /setup/ or routes defined in routes.lua) without authentication.Affected if The setup routes are accessible without requiring authentication credentials.
A system is affected if Q-Free MaxTime version 2.11.0 or prior is installed and the device web interface (including the setup routes) is accessible to untrusted network segments.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Q-Free MaxTime to a version greater than 2.11.0. As a compensating control, restrict network access to the device's web interface to trusted IP addresses or place behind a VPN/authenticated proxy.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26366 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data