CVE-2025-26352
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-35 "Path Traversal" in the template deletion mechanism in Q-Free MaxTime less than or equal to version 2.11.0 allows an authenticated remote attacker to delete sensitive files 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 confidenceQ-Free MaxTime versions 2.11.0 and prior contain a path traversal vulnerability (CWE-35) in the template deletion functionality. An authenticated attacker can manipulate file path parameters in HTTP requests to escape the intended directory and delete arbitrary files on the server filesystem accessible to the web application process.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
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 installationSearch for MaxTime web application files, typically installed in C:\Program Files\Q-Free\MaxTime or /opt/qfree/maxtime. Check for maxtime.exe, MaxTime web.config, or associated DLLs.Affected if Q-Free MaxTime software is found on the system
-
Determine installed MaxTime versionLocate the MaxTime application directory and check version info. Common locations: the application's about page, version.dll, or check Windows registry under HKLM\SOFTWARE\Q-Free\MaxTime for a Version value.Affected if Installed version is 2.11.0 or lower
-
Verify template deletion endpoint is accessibleCheck web server configuration (IIS or embedded) for MaxTime application. Look for endpoints handling template deletion, typically URLs containing '/template/delete' or similar patterns in the web.config or route configuration.Affected if Template deletion functionality is exposed via HTTP
-
Review web server access logs for traversal patternsExamine IIS or embedded web server logs in the MaxTime logs directory for requests containing '../' sequences, especially targeting template deletion endpoints. Look for unusual patterns like ../../windows/system32 or similar path escape attempts.Affected if Logs show requests with '../' sequences to template deletion endpoints
-
Check for unauthorized file deletion indicatorsReview file system for unexpected deletions in directories outside the intended template storage folder. Compare current state against known-good backups or check file system journaling for recent delete operations on system-critical files.Affected if Files outside the expected template directory have been deleted
A system is affected if Q-Free MaxTime version 2.11.0 or lower is installed and the template deletion HTTP endpoint is accessible, or if logs or file system evidence shows path traversal exploitation attempts.
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 dataApply vendor patch or upgrade to MaxTime version greater than 2.11.0. If no patch available, implement strict input validation and whitelist-based path verification for the template deletion endpoint to prevent traversal sequences (../).
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26352 — 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-26352 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