dbcve.org
MaxtimeApplication · Q Free

CVE-2025-26362

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 set an arbitrary authentication profile server 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 confidence

The maxprofile/setup/routes.lua component in Q-Free MaxTime version 2.11.0 and below lacks authentication checks on critical endpoints, allowing unauthenticated remote attackers to modify authentication profile server settings via crafted HTTP requests. This CWE-306 vulnerability enables complete bypass of the authentication mechanism for profile configuration.

MitigationImplement proper authentication and authorization checks on all routes in setup/routes.lua, or upgrade to a patched version if available. Consider network segmentation to limit exposure of the administrative 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
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. Identify MaxTime installation version
    Locate the MaxTime installation directory and check version information in the product metadata, about page, or version file. Common locations include the installation root, a VERSION file, or the application properties/configuration.
    Affected if Installed version is 2.11.0 or lower
  2. Verify vulnerable component exists
    Check for the presence of the maxprofile/setup/routes.lua file within the MaxTime installation directory structure.
    Affected if The file maxprofile/setup/routes.lua exists in the installation
  3. Test setup endpoint accessibility
    Send an HTTP GET request to the setup/routes endpoint (e.g., /maxprofile/setup/routes or similar path) without providing any authentication credentials.
    Affected if The endpoint responds with HTTP 200 and returns data without requiring authentication
  4. Verify authentication bypass on configuration endpoints
    Send an HTTP POST or PUT request to the profile server configuration endpoints defined in setup/routes.lua without any authentication tokens or session cookies.
    Affected if The request succeeds and modifies profile server settings without authentication

User is affected if MaxTime version 2.11.0 or below is installed AND the setup/routes endpoints are accessible without any authentication credentials.

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

Implement proper authentication and authorization checks on all routes in setup/routes.lua, or upgrade to a patched version if available. Consider network segmentation to limit exposure of the administrative interface.

Recommended fix Moderate confidence

Upgrade to Maxtime version greater than 2.11.0 (e.g., latest stable release)

  1. 1. Identify the current Maxtime version installed by checking the system documentation or web interface.
  2. 2. Upgrade Maxtime to a version greater than 2.11.0 (the latest stable release that includes the security fix).
  3. 3. After upgrading, verify that the maxprofile/setup/routes.lua endpoint now requires proper authentication.
  4. 4. Test that legitimate configuration of authentication profile servers still functions correctly after the upgrade.
  5. 5. Confirm the vulnerability is remediated by reviewing release notes or patch documentation for the new version.

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

Fix this in Maxtime Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26362 — 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-26362 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