CVE-2025-26373
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 (user endpoint) in Q-Free MaxTime less than or equal to version 2.11.0 allows an authenticated (low-privileged) attacker to enumerate users 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 CWE-862 Missing Authorization vulnerability exists in the maxprofile/users/routes.lua user endpoint of Q-Free MaxTime version 2.11.0 and below. The endpoint lacks proper authorization checks, allowing authenticated low-privileged users to enumerate other users in the system through crafted HTTP requests.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 installed MaxTime versionLocate the MaxTime application and check its version number (typically found in about dialog, installation directory, or by querying the application directly)Affected if Installed version is 2.11.0 or lower
-
Verify the maxprofile module existsCheck if the maxprofile/users/routes.lua endpoint file exists in the MaxTime installation directoryAffected if The routes.lua file exists in the maxprofile/users directory
-
Confirm low-privileged user access to user endpointUsing a low-privileged authenticated account, send an HTTP request to the user enumeration endpoint (typically /maxprofile/users or similar path) without elevated permissionsAffected if The endpoint returns user data or user list information without requiring elevated/privileged session credentials
You are affected if MaxTime version 2.11.0 or lower is installed AND the maxprofile/users endpoint is accessible to low-privileged authenticated users without 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 proper role-based authorization checks on the user endpoint to ensure only privileged users can access user enumeration functionality, and validate that the requesting user has appropriate permissions before returning user data.
Any version greater than 2.11.0 (e.g., 2.11.1 or latest stable release)
- 1. Identify the current Q-Free MaxTime software version currently installed
- 2. Check Q-Free's official support channels or vendor documentation for the latest stable release
- 3. Upgrade the Maxtime installation to a version higher than 2.11.0 (e.g., 2.11.1 or later)
- 4. After upgrade, verify that the authorization controls on the user endpoint are properly enforced
- 5. Confirm that low-privileged users can no longer enumerate user accounts through the maxprofile/users/routes.lua endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26373 — 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-26373 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