CVE-2024-44065
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 · uneditedTime-based blind SQL Injection vulnerability in Cloudlog v2.6.15 at the endpoint /index.php/logbookadvanced/search in the qsoresults parameter.
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 confidenceTime-based blind SQL injection vulnerability in Cloudlog v2.6.15 at the /index.php/logbookadvanced/search endpoint via the qsoresults parameter. This allows unauthenticated attackers to inject malicious SQL queries that execute based on time delays, potentially exfiltrating sensitive data from the database.
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.6.15CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Cloudlog installation versionLocate the version file or header in the Cloudlog installation (commonly found in a version.php file, composer.json, or admin interface). Compare the installed version to the affected version 2.6.15.Affected if The installed version is exactly 2.6.15.
-
Confirm logbookadvanced endpoint existsCheck if the file path /index.php/logbookadvanced/search is accessible on the web server. This is the vulnerable endpoint where the qsoresults parameter is processed.Affected if The endpoint exists and responds to requests.
-
Verify qsoresults parameter handlingExamine the application source code or HTTP traffic to determine if the qsoresults parameter from the /logbookadvanced/search endpoint is passed directly into SQL queries without sanitization, prepared statements, or input validation.Affected if The qsoresults parameter is used in SQL queries without parameterized queries or input validation.
-
Check for time-delay behavior (optional confirmation)If authorized and within scope, send a crafted qsoresults value containing time-delay syntax (such as SLEEP commands) to the endpoint and observe whether the response time increases accordingly. This confirms the time-based blind SQL injection exists.Affected if The application exhibits delayed responses correlating to injected time-based SQL commands.
A user is affected if they are running Cloudlog version 2.6.15 and the logbookadvanced/search endpoint with the qsoresults parameter is accessible without proper input sanitization on the SQL queries.
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 dataUpgrade to a patched version of Cloudlog if available, or implement proper input validation and parameterized queries/prepared statements at the identified endpoint to neutralize SQL injection vectors.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44065 — 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-2024-44065 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