CVE-2025-26370
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/user-groups/routes.lua in Q-Free MaxTime less than or equal to version 2.11.0 allows an authenticated (low-privileged) attacker to remove privileges from user groups 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 missing authorization check in maxprofile/user-groups/routes.lua of Q-Free MaxTime allows authenticated low-privileged users to remove privileges from user groups through crafted HTTP requests. The vulnerability stems from the route handler not verifying that the requesting user has sufficient permissions before allowing modification of user group privileges.
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
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
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 Q-Free MaxTime installation directory and determine the installed version number. Common locations include /opt/maxtime, /var/www/maxtime, or the application's root directory. Check for version files, about pages, or API endpoints that expose version information.Affected if Installed version is 2.11.0 or lower (or version cannot be determined and the product is Q-Free MaxTime)
-
Locate the user-groups route handlerFind the file maxprofile/user-groups/routes.lua within the MaxTime installation. This file handles HTTP requests related to user group management privileges.Affected if The file exists and is part of the deployed MaxTime application
-
Inspect authorization logic in routes.luaExamine the route handler code in routes.lua for any permission validation before privilege modification operations. Look for function calls that verify the requesting user's role or privilege level before allowing add/remove privilege actions.Affected if No authorization check is present before privilege modification logic, or the code only validates authentication without checking elevated privileges
-
Verify low-privileged user accessUsing a low-privileged (non-admin) authenticated user account, attempt to send HTTP requests to modify user group privileges through the user-groups API endpoints. Observe whether the requests succeed despite insufficient permissions.Affected if Low-privileged users can successfully remove or modify privileges on user groups
A user is affected if they have Q-Free MaxTime version 2.11.0 or lower installed and the maxprofile/user-groups/routes.lua file lacks proper authorization checks before allowing privilege modifications.
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 dataImplement proper authorization checks in the user-groups route to verify that only users with elevated privileges can modify user group permissions. Consider role-based access control (RBAC) validation before executing privilege modification operations.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26370 — 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-26370 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