dbcve.org
MaxtimeApplication · Q Free

CVE-2025-26346

HIGH · 7.6 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to after 2.11.0 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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-89 "Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')" in maxprofile/menu/model.lua (editUserGroupMenu endpoint) in Q-Free MaxTime less than or equal to version 2.11.0 allows an authenticated remote attacker to execute arbitrary SQL commands 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

SQL injection vulnerability in the editUserGroupMenu endpoint of Q-Free MaxTime (versions <= 2.11.0) allows authenticated remote attackers to execute arbitrary SQL commands through unsanitized input in the maxprofile/menu/model.lua file.

MitigationUpgrade to a version greater than 2.11.0, or implement parameterized queries/prepared statements in the affected endpoint to neutralize SQL special characters in user input.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

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. Identify MaxTime installation version
    Locate the version information for your Q-Free MaxTime installation. This is typically found in the application itself, an about page, installation files, or version logs. Common locations include the web interface header/footer, a /about endpoint, or version metadata files in the installation directory.
    Affected if The installed version is 2.11.0 or any earlier version (anything <= 2.11.0)
  2. Verify presence of vulnerable file
    Check if the file maxprofile/menu/model.lua exists in your MaxTime installation directory. This file contains the editUserGroupMenu endpoint handler.
    Affected if The file exists and the application version is <= 2.11.0
  3. Confirm endpoint accessibility
    Determine if the editUserGroupMenu endpoint is accessible on your MaxTime server. This endpoint typically handles menu configuration for user groups and is accessed via the web interface.
    Affected if The endpoint is exposed and the installation is version <= 2.11.0
  4. Check authentication configuration
    Review your MaxTime authentication settings to determine what users have access to the editUserGroupMenu functionality. The vulnerability requires an authenticated session to exploit.
    Affected if Authenticated users with menu configuration privileges exist and the version is <= 2.11.0

Your environment is affected if Q-Free MaxTime version is 2.11.0 or lower AND the editUserGroupMenu endpoint in maxprofile/menu/model.lua is accessible to authenticated users.

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

Upgrade to a version greater than 2.11.0, or implement parameterized queries/prepared statements in the affected endpoint to neutralize SQL special characters in user input.

Recommended fix Moderate confidence

Any version higher than 2.11.0 (contact Q-Free for the specific fixed release)

  1. 1. Verify current MaxTime installation version by checking the application interface or system documentation
  2. 2. Confirm the installation is version 2.11.0 or below, which is affected by CVE-2025-26346
  3. 3. Contact Q-Free support or check official Q-Free channels for the latest stable release that includes the fix for this SQL injection vulnerability
  4. 4. Plan maintenance window for the upgrade procedure
  5. 5. Perform a full backup of the MaxTime database and configuration before upgrading
  6. 6. Upgrade MaxTime to a version higher than 2.11.0 (the fixed release)
  7. 7. After upgrade, verify the editUserGroupMenu endpoint is accessible and functional
  8. 8. Validate that the SQL injection vulnerability is remediated by confirming the fix is applied
Caveat Review Q-Free release notes for any configuration or behavioral changes between versions

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26346 — 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-26346 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