CVE-2024-48255
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 · uneditedCloudlog 2.6.15 allows Oqrs.php get_station_info station_id SQL injection.
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 confidenceCloudlog 2.6.15 contains a SQL injection vulnerability in the Oqrs.php file, specifically in the get_station_info function where the station_id parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.
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.
-
Confirm Cloudlog installation and versionLocate the Cloudlog installation directory and identify the installed version number (commonly found in a version file, about page, or composer.json)Affected if The installed version is exactly 2.6.15 (any other version is not affected by this CVE)
-
Verify OQRS module is accessibleDetermine whether the OQRS (Online QSL Request System) feature is enabled or configured on the installation - check application configuration or routes for Oqrs.php accessAffected if OQRS is accessible and the get_station_info function can be reached via HTTP request without authentication
-
Locate the vulnerable Oqrs.php fileFind the Oqrs.php file within the Cloudlog application directory structure and verify it contains the get_station_info functionAffected if The file exists and contains the get_station_info function with a station_id parameter used in a raw SQL query
-
Inspect SQL query implementationExamine the get_station_info function in Oqrs.php to confirm the station_id parameter is used directly in an SQL query without parameterized statements or prepared statementsAffected if The station_id parameter is concatenated directly into an SQL query without binding or escaping
-
Verify unauthenticated accessConfirm the vulnerable endpoint does not require authentication (the CVE states it is exploitable by unauthenticated attackers)Affected if The OQRS endpoint handling station_id is accessible without login or authentication token
You are affected only if running Cloudlog version 2.6.15, the OQRS module is enabled, and the station_id parameter in Oqrs.php get_station_info function uses unsanitized input in SQL queries accessible without authentication.
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. Until then, implement strict input validation on the station_id parameter and refactor vulnerable queries to use parameterized queries or prepared statements.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-48255 — 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-48255 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