CVE-2025-26358
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-15 "External Control of System or Configuration Setting" in ldbMT.so in Q-Free MaxTime less than or equal to version 2.11.0 allows an authenticated remote attacker to modify system configuration 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 · moderate confidenceThis is a CWE-15 (External Control of System or Configuration Setting) vulnerability in the ldbMT.so component of Q-Free MaxTime traffic management software. An authenticated remote attacker can modify system configuration settings by sending crafted HTTP requests to the affected component in versions 2.11.0 and earlier.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 software versionLocate and inspect the installed MaxTime version using system inventory tools, software packaging utilities, or check the application binary/dll version properties. Look for version strings in the application directory or Windows Registry if on Windows-based installations.Affected if The installed version is 2.11.0 or earlier.
-
Confirm presence of ldbMT.so componentSearch for the file ldbMT.so in the MaxTime installation directory or associated library paths. On Windows this may appear as ldbMT.dll. Use file system search or inspect application module listings.Affected if The ldbMT.so (or ldbMT.dll) component exists in the MaxTime installation.
-
Verify HTTP administrative interface accessibilityCheck network configuration to determine if the MaxTime web interface (typically on ports 80/443 or custom HTTP ports used by traffic management systems) is accessible from network segments outside the trusted administrative zone. Review firewall rules and reverse proxy configurations.Affected if The administrative HTTP interface is reachable from untrusted network segments.
-
Review authentication configuration for ldbMTInspect the MaxTime configuration files or administrative settings related to the ldbMT component to verify whether authentication is properly enforced on configuration modification endpoints. Check for any misconfigured permissions allowing unauthenticated or weakly authenticated access.Affected if Authentication on the ldbMT configuration endpoints is disabled, weakened, or permits unauthorized modification by authenticated users.
A system is affected if it runs MaxTime version 2.11.0 or earlier with the ldbMT.so component enabled and its HTTP administrative interface accessible to authenticated attackers.
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 dataUpdate to a version greater than 2.11.0 once the vendor patch is available, and ensure strict access controls on administrative interfaces to limit exposure to authenticated attackers.
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26358 — 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-26358 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