dbcve.org
MaxtimeApplication · Q Free

CVE-2025-26360

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to after 2.11.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
A CWE-306 "Missing Authentication for Critical Function" in maxprofile/persistance/routes.lua in Q-Free MaxTime less than or equal to version 2.11.0 allows an unauthenticated remote attacker to delete dashboards 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 confidence

Q-Free MaxTime versions 2.11.0 and earlier contain a CWE-306 vulnerability in the maxprofile/persistence/routes.lua file where the dashboard deletion endpoint lacks authentication checks, allowing any remote attacker to delete dashboards via crafted HTTP requests without providing valid credentials.

MitigationImplement proper authentication and authorization checks on the dashboard deletion endpoint in routes.lua to ensure only authenticated and authorized users can delete dashboards. Consider applying the principle of least privilege.

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
MaxtimeApplication
Affected:<= 2.11.0

CVSS 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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Q-Free MaxTime is installed
    Locate the MaxTime application installation directory. Common paths may include /opt/maxtime, /usr/local/maxtime, or within a web server's document root. Look for the maxprofile directory structure.
    Affected if The application is not present on the system
  2. Identify installed MaxTime version
    Check the version file or application metadata within the MaxTime installation directory. Common locations include a VERSION file, about dialog, or the main executable's properties.
    Affected if The installed version is 2.11.0 or any version earlier than 2.11.0
  3. Locate the vulnerable routes.lua file
    Navigate to the maxprofile/persistence/ subdirectory within the MaxTime installation and locate the routes.lua file. This file contains the HTTP endpoint definitions.
    Affected if The file maxprofile/persistence/routes.lua exists and contains dashboard-related route definitions
  4. Inspect dashboard deletion endpoint for authentication
    Open routes.lua and locate the function or route handler responsible for dashboard deletion (often named delete, remove, or a similar term). Examine whether the function contains any authentication validation such as session checks, token validation, or privilege verification before executing the delete operation.
    Affected if The dashboard deletion endpoint function does not contain any authentication, authorization, or session validation logic

A user is affected if Q-Free MaxTime version 2.11.0 or earlier is installed AND the routes.lua file contains a dashboard deletion endpoint that lacks any form of authentication or authorization check before allowing deletion.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.11.0
Interim mitigation

Implement proper authentication and authorization checks on the dashboard deletion endpoint in routes.lua to ensure only authenticated and authorized users can delete dashboards. Consider applying the principle of least privilege.

Recommended fix Moderate confidence

Version higher than 2.11.0 (contact Q-Free support for exact fixed release)

  1. Identify the current Q-Free MaxTime version in use
  2. Contact Q-Free official support or channels to obtain the latest version that addresses CVE-2025-26360
  3. Plan an upgrade to a version higher than 2.11.0, ensuring the release notes confirm the fix for the missing authentication vulnerability in maxprofile/persistance/routes.lua
  4. Schedule maintenance window and backup current configuration
  5. Perform upgrade following Q-Free's official upgrade documentation
  6. Verify the vulnerability is resolved by attempting the previously vulnerable HTTP request path (should require authentication or be blocked)
Caveat Review release notes for any configuration or behavioral changes between current version and new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Maxtime Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26360 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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