dbcve.org
MaxtimeApplication · Q Free

CVE-2025-26365

HIGH · 7.5 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to after 2.11.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A 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 enable 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 · moderate confidence

A missing authentication vulnerability in maxprofile/setup/routes.lua of Q-Free MaxTime versions 2.11.0 and earlier allows unauthenticated remote attackers to manipulate front panel authentication settings via crafted HTTP requests. The critical function (enabling/disabling authentication) can be accessed without any authentication, enabling an attacker to modify security controls.

MitigationApply vendor patch for MaxTime version > 2.11.0 immediately. Until patched, restrict network access to the /setup/ endpoints via firewall or VPN, and monitor for unauthorized changes to authentication configuration.

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
MaxtimeApplication
Affected:<= 2.11.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MaxTime installation and version
    Identify if Q-Free MaxTime is installed and determine the installed version by checking the product documentation, about page, or version file. Compare against the affected range: versions 2.11.0 and earlier.
    Affected if MaxTime version is 2.11.0 or earlier
  2. Verify network exposure of /setup/ endpoints
    Scan or review network access controls to determine if the /setup/ routes (specifically /setup/routes.lua) are accessible from untrusted networks or the internet.
    Affected if The /setup/ endpoints are exposed to unauthenticated network access
  3. Inspect authentication configuration settings
    Review the current authentication settings in MaxTime (front panel authentication on/off status, user accounts, access controls) and compare against known-good baseline configurations.
    Affected if Authentication settings have been modified from their expected state or authentication has been disabled
  4. Check for unauthorized changes in authentication logs
    Review MaxTime logs, system audit logs, or security event logs for any modifications to authentication configuration that were performed from IP addresses or sessions that should not have had access.
    Affected if Logs show authentication configuration changes from unexpected sources or at unexpected times

A user is affected if they are running MaxTime version 2.11.0 or earlier AND the /setup/ endpoints are network-accessible, allowing unauthenticated attackers to modify authentication settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.11.0
Interim mitigation

Apply vendor patch for MaxTime version > 2.11.0 immediately. Until patched, restrict network access to the /setup/ endpoints via firewall or VPN, and monitor for unauthorized changes to authentication configuration.

Recommended fix Moderate confidence

Q-Free MaxTime version > 2.11.0 (contact Q-Free for the specific fixed release)

  1. Identify the current Maxtime version in use by checking the application's about page or system information
  2. Download the latest Maxtime release from the official Q-Free vendor channels
  3. Review the vendor release notes to confirm the version includes the fix for CVE-2025-26365
  4. Schedule a maintenance window for the upgrade process
  5. Back up the current Maxtime configuration and database before proceeding
  6. Stop the Maxtime services
  7. Install the new Maxtime version (> 2.11.0) following the vendor's upgrade documentation
  8. Restore the backed-up configuration
Caveat Review vendor release notes for any configuration or compatibility changes between your current version and the new release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Maxtime Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26365 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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