CVE-2025-26359
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/accounts/routes.lua in Q-Free MaxTime less than or equal to version 2.11.0 allows an unauthenticated remote attacker to reset user PINs 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 confidenceA critical authentication bypass exists in maxprofile/accounts/routes.lua in Q-Free MaxTime version 2.11.0 and prior. The PIN reset endpoint lacks authentication checks, allowing any unauthenticated remote attacker to reset arbitrary user PINs via crafted HTTP requests to the accounts routes.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 MaxTime installation and versionLocate the MaxTime installation directory and check the version file or application metadata. Common locations may include /opt/maxtime, /usr/local/maxtime, or the application's installation folder. Look for version information in configuration files, About dialogs, or the application banner.Affected if The installed version is 2.11.0 or any prior version (lower version numbers indicate the vulnerability is present.
-
Locate the accounts routes moduleSearch for the file routes.lua within the maxprofile/accounts directory structure in the MaxTime installation folder. This file handles the accounts-related HTTP endpoints including PIN reset functionality.Affected if The file maxprofile/accounts/routes.lua exists in the installation, indicating the vulnerable component is present.
-
Verify PIN reset endpoint exposureExamine the routes.lua file for PIN reset endpoint definitions. Look for route handlers that process PIN reset requests, typically at paths like /accounts/resetpin, /accounts/pin/reset, or similar patterns. Check if these endpoints are publicly accessible without authentication requirements.Affected if A PIN reset route handler exists in routes.lua without authentication middleware or access control checks.
-
Test endpoint authentication (if safe to do so)Send a crafted HTTP request to the suspected PIN reset endpoint (such as POST /accounts/resetpin or similar path found in routes.lua) without providing authentication credentials. Observe whether the request is accepted or rejected. Only perform this on non-production systems or with explicit authorization.Affected if The PIN reset endpoint accepts and processes unauthenticated requests, returning a successful response rather than an authentication error (401/403).
A system is affected if Q-Free MaxTime version 2.11.0 or prior is installed and the PIN reset endpoint in maxprofile/accounts/routes.lua is accessible without authentication.
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 dataUpgrade MaxTime to a version greater than 2.11.0 which includes proper authentication for the PIN reset functionality. If patching is immediately infeasible, restrict network access to the affected endpoints via firewall or VPN.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26359 — 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-26359 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