CVE-2025-26341
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 arbitrary user passwords 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 password reset endpoint in maxprofile/accounts/routes.lua of Q-Free MaxTime lacks authentication checks, allowing any unauthenticated attacker to reset arbitrary user passwords by sending crafted HTTP requests to the endpoint.
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 the MaxTime installationLocate the MaxTime application installation directory and check for version information in version files, about pages, or application metadataAffected if The installed version is Q-Free MaxTime version 2.11.0 or lower
-
Check the affected file presenceInspect the file maxprofile/accounts/routes.lua within the MaxTime installation directory for the password reset endpoint handlerAffected if The file exists and contains password reset route definitions without authentication middleware
-
Verify password reset endpoint accessibilitySend a crafted HTTP POST request to the password reset endpoint (typically /accounts/reset or /password/reset path) without providing valid authentication credentialsAffected if The endpoint accepts the request and returns a success response without requiring authentication tokens or session cookies
-
Inspect route configuration for authenticationExamine the Lua code in maxprofile/accounts/routes.lua to determine if the password reset route has any authentication or authorization guards definedAffected if The route handler lacks authentication checks (no middleware, no session validation, no token verification)
-
Cross-reference with known vulnerable version rangeCompare your installed MaxTime version against the affected range: versions 2.11.0 and belowAffected if Your version is 2.11.0 or lower and exhibits the unauthenticated password reset behavior
You are affected if MaxTime version 2.11.0 or lower is installed and the password reset endpoint in maxprofile/accounts/routes.lua accepts unauthenticated requests to reset arbitrary user passwords.
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 MaxTime to version greater than 2.11.0 to receive the vendor patch, or implement proper authentication and authorization checks on the password reset route.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26341 — 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-26341 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