CVE-2025-1101
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-204 "Observable Response Discrepancy" in the login page in Q-Free MaxTime less than or equal to version 2.11.0 allows an unauthenticated remote attacker to enumerate valid usernames 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 login page in Q-Free MaxTime versions 2.11.0 and below exhibits observable response discrepancies (CWE-204) that allow unauthenticated remote attackers to enumerate valid usernames by analyzing differences in HTTP responses when submitting login attempts with various username combinations.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Q-Free MaxTime installation and versionCheck the application's version information, typically found in the product UI under Help/About, or in installation directories, configuration files, or banner/graceful endpoints that expose version detailsAffected if The installed version is Q-Free MaxTime version 2.11.0 or any earlier version
-
Confirm login page is network accessibleVerify the web-based login interface is reachable over the network. This is typically at a path like /login, /auth, or the root URL of the applicationAffected if The login page is exposed to network access (especially untrusted networks or the internet)
-
Test for username enumeration via response differencesSubmit two login attempts with different usernames (one likely-valid and one clearly-invalid) and compare the HTTP response status codes, response body content, or error messages. Use a tool like curl or Burp Suite to capture and compare responsesAffected if The responses differ noticeably between valid and invalid usernames (e.g., different error messages, different HTTP status codes, or different response timing)
-
Check for uniform error messagingInspect the login failure responses for both valid and invalid usernames. Look for differences in error text such as 'Invalid username' vs 'Invalid password', or any indication that the username was recognizedAffected if Error messages reveal whether a username exists in the system (e.g., 'User does not exist' for invalid usernames vs 'Incorrect password' for valid ones)
You are affected if Q-Free MaxTime version 2.11.0 or lower is installed with an accessible login page that exhibits different responses for valid versus invalid usernames.
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 uniform error messages and response timing for both valid and invalid usernames to eliminate observable differences, or implement rate limiting/account lockout mechanisms to prevent automated username enumeration.
Version > 2.11.0 (contact vendor for specific fixed release)
- Upgrade Q-Free MaxTime to a version greater than 2.11.0
- After upgrading, verify that the login page no longer reveals different responses for valid vs invalid usernames
- Confirm the fix by testing with both valid and invalid usernames to ensure uniform response behavior
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-1101 — 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-1101 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