CVE-2025-26368
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 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 confidenceQ-Free MaxTime versions 2.11.0 and earlier contain a missing authorization vulnerability in the user groups endpoint (maxprofile/user-groups/routes.lua). An authenticated low-privileged user can send crafted HTTP requests to remove user groups without proper authorization checks, allowing privilege escalation to administrative functions.
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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 information. Common locations may include /opt/maxtime, the application's about page, or installation metadata.Affected if The installed version is 2.11.0 or earlier.
-
Locate the user-groups endpoint fileSearch for the file maxprofile/user-groups/routes.lua in the installation directory.Affected if The file exists in the installation, indicating the vulnerable endpoint is present.
-
Inspect authorization logic in routes.luaExamine the routes.lua file for delete or remove operations on user groups. Look for authorization or permission checks before executing delete actions.Affected if The file lacks or has weak authorization checks before allowing group deletion operations.
-
Verify low-privileged user accessLog in with a low-privileged (non-administrator) user account and attempt to access the user groups deletion endpoint via HTTP request.Affected if The low-privileged user can successfully delete user groups without receiving authorization errors.
-
Check role enforcement on administrative functionsReview user role configurations and test whether non-administrative accounts can modify or delete administrative elements like user groups.Affected if Non-administrative users can perform administrative operations such as removing user groups.
The environment is affected if MaxTime version 2.11.0 or earlier is installed AND the user-groups endpoint allows low-privileged authenticated users to delete groups without proper authorization checks.
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.
dbcve · scopedImplement role-based authorization checks in routes.lua to verify user permissions before allowing group removal operations; restrict delete actions to administrators only.
Q-Free MaxTime version greater than 2.11.0 (contact Q-Free vendor for exact fixed release)
- 1. Identify the current Maxtime version by checking the system administration interface or running 'maxprofile --version'
- 2. Back up the current Maxtime configuration and database before performing any upgrade
- 3. Obtain the latest version of Q-Free MaxTime from the official vendor (Q-Free) - contact vendor support or visit their official channels to obtain version information newer than 2.11.0
- 4. Follow the vendor's official upgrade procedure documentation for Maxtime
- 5. After upgrade, verify the maxprofile/user-groups/routes.lua component has been updated
- 6. Test that authenticated users can only modify user groups they are authorized to access
- 7. Verify the fix by attempting a low-privileged user to remove user groups - this should now be properly authorized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26368 — 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-26368 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