CVE-2025-26348
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-89 "Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')" in maxprofile/menu/model.lua (editUserMenu 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 confidenceSQL injection vulnerability in the editUserMenu endpoint of Q-Free MaxTime (maxprofile/menu/model.lua) allows authenticated remote attackers to execute arbitrary SQL commands through crafted HTTP requests due to improper neutralization of special elements in SQL queries.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify MaxTime installation pathLocate the Q-Free MaxTime installation directory on the system. Look for directories containing 'maxprofile' or 'menu' folders, typically under the web server root or application installation directory.Affected if Cannot locate MaxTime installation or related directories on the system (product may not be installed).
-
Verify the vulnerable component existsCheck for the presence of the file maxprofile/menu/model.lua in the MaxTime installation directory. This is the file containing the vulnerable editUserMenu function.Affected if The file maxprofile/menu/model.lua does not exist (the vulnerable code is not present).
-
Confirm MaxTime versionLocate and read the MaxTime version information, typically found in version files, about pages, or the application metadata. Compare the installed version number to the affected range.Affected if Installed version is 2.11.0 or lower.
-
Identify if editUserMenu endpoint is exposedReview web server configuration or application routing to determine if the /editUserMenu or similar endpoint is accessible via HTTP. Check for URL patterns like /maxprofile/menu/model.lua or REST endpoints handling menu editing.Affected if The editUserMenu functionality is exposed and accessible via HTTP requests.
The environment is affected if Q-Free MaxTime version 2.11.0 or lower is installed and the maxprofile/menu/model.lua file with the editUserMenu endpoint is present and accessible.
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 requires implementing parameterized queries or proper input validation/sanitization in the editUserMenu function within model.lua. All user-supplied input to this endpoint must be safely escaped or replaced with bound parameters before SQL execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26348 — 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-26348 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