CVE-2025-1102
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-346 "Origin Validation Error" in the CORS configuration in Q-Free MaxTime less than or equal to version 2.11.0 allows an unauthenticated remote attacker to affect the device confidentiality, integrity, or availability via crafted URLs or 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 · moderate confidenceThis is a CORS (Cross-Origin Resource Sharing) misconfiguration vulnerability in Q-Free MaxTime version 2.11.0 and below. The application fails to properly validate the Origin header in incoming HTTP requests, allowing an unauthenticated remote attacker to make cross-origin requests from malicious websites. This bypasses the Same-Origin Policy protections and can be exploited to perform actions on behalf of legitimate users or access sensitive data.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 MaxTime versionLocate and check the installed version of Q-Free MaxTime in the application (typically found in About section, version file, or HTTP banner)Affected if Version is 2.11.0 or lower
-
Examine CORS configuration for Origin validationInspect the application's CORS settings to determine if it validates the Origin header against an allowlist or accepts all origins indiscriminatelyAffected if CORS configuration lacks proper Origin header validation or uses wildcard (*) origins
-
Confirm web interface exposureDetermine if the MaxTime web interface is accessible over HTTP/HTTPS, as the vulnerability is exploitable via incoming HTTP requestsAffected if Web interface is exposed and accessible to untrusted networks
-
Probe Origin header response behaviorSend a test HTTP request with an arbitrary Origin value (for example, http://malicious-site.com) to the MaxTime server and examine the Access-Control-Allow-Origin response headerAffected if Server returns the arbitrary Origin in Access-Control-Allow-Origin without rejection
The environment is affected if MaxTime version is 2.11.0 or lower AND the server does not properly validate the Origin header in incoming requests.
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 dataFix the CORS configuration to properly validate the Origin header against an explicit allowlist of permitted origins. Disable wildcard (*) origins and ensure the server rejects requests from untrusted origins.
- Consultation3.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1102 — 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-1102 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