CVE-2025-26378
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-862 "Missing Authorization" in maxprofile/users/routes.lua in Q-Free MaxTime less than or equal to version 2.11.0 allows an authenticated (low-privileged) attacker to reset passwords, including the ones of administrator accounts, 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 vulnerability exists in maxprofile/users/routes.lua where password reset functionality lacks proper authorization checks. An authenticated low-privileged user can send crafted HTTP requests to reset passwords for any account, including administrator accounts. This is a classic CWE-862 (Missing Authorization) where the application fails to verify if the requesting user has permission to modify privileged account credentials.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 application installation directory and check the version file or product metadata. Common locations include /opt/maxtime, /usr/local/maxtime, or within the application's config file. Look for a version manifest, about page, or config file that displays the installed version number.Affected if The installed version of Q Free Maxtime is 2.11.0 or lower.
-
Locate the vulnerable routes.lua fileNavigate to the maxprofile/users/ directory within the Maxtime installation. Identify the routes.lua file. This file contains the password reset endpoint definitions.Affected if The file maxprofile/users/routes.lua exists in the installation, indicating the vulnerable code path is present.
-
Verify password reset endpoint existsExamine routes.lua for the password reset endpoint definition. Look for routes handling password reset requests, typically with paths like /password/reset, /users/reset_password, or similar patterns. Confirm the endpoint is registered and accessible.Affected if A password reset endpoint is defined in routes.lua and appears to be active.
-
Check for authorization logic in password reset handlerReview the password reset handler function in routes.lua. Search for authorization checks that verify the requesting user has permission to reset the target account password. Look for code that validates user roles, permissions, or ownership before processing the reset request.Affected if No authorization check exists before processing password reset requests, or the check can be bypassed by authenticated low-privilege users.
You are affected if Q Free Maxtime version 2.11.0 or lower is installed and the password reset endpoint in maxprofile/users/routes.lua lacks proper authorization validation before allowing password changes for any account.
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 dataApply vendor patch/upgrade to MaxTime version greater than 2.11.0. Until patched, restrict network access to administrative interfaces, monitor for suspicious password reset activity, and consider disabling the password reset functionality if not business-critical.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26378 — 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-26378 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