dbcve.org
Cab Management SystemApplication · Oretnom23

CVE-2024-51030

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A SQL injection vulnerability in manage_client.php and view_cab.php of Sourcecodester Cab Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the id parameter, leading to unauthorized access and potential compromise of sensitive data within the database.

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 confidence

SQL injection vulnerability in the id parameter of manage_client.php and view_cab.php in Sourcecodester Cab Management System 1.0 allows remote attackers to execute arbitrary SQL commands via unsanitized user input, potentially leading to unauthorized database access and data exfiltration.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) and implement proper input validation on the id parameter and all user-supplied inputs.

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
Cab Management SystemApplication
Affected:= 1.0

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cab Management System installation
    Locate the web application directory - look for folders containing 'cab', 'manage_client.php', or 'view_cab.php'. Check web server document root for Sourcecodester or Oretnom23 Cab Management System files.
    Affected if The application directory contains manage_client.php and view_cab.php files from Oretnom23 Cab Management System version 1.0
  2. Verify the vulnerable files exist
    Confirm presence of both manage_client.php and view_cab.php in the web application directory.
    Affected if Both manage_client.php and view_cab.php files exist in the application
  3. Check if the id parameter is processed in the files
    Open manage_client.php and view_cab.php in a text editor and search for code that retrieves the 'id' parameter using $_GET or $_POST (e.g., $_GET['id'], $_POST['id'], or $_REQUEST['id']).
    Affected if The files contain code that retrieves an 'id' parameter from user input without sanitization
  4. Inspect SQL query construction
    In the same files, locate SQL query statements (SELECT, INSERT, UPDATE, DELETE) and check if the 'id' parameter is concatenated directly into the query string rather than using prepared statements or parameterized queries.
    Affected if SQL queries contain the 'id' parameter embedded directly without using bind parameters or escaping functions
  5. Verify the application is web-accessible
    Attempt to access the affected PHP files via HTTP/HTTPS request using a browser or curl tool, for example: http://your-server/cab/manage_client.php?id=1
    Affected if The web server serves the application and the affected files are accessible over the network

A user is affected if Oretnom23 Cab Management System 1.0 is installed, the manage_client.php and view_cab.php files are present, and the 'id' parameter is used in SQL queries without prepared statements or input sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries (prepared statements) and implement proper input validation on the id parameter and all user-supplied inputs.

Fix this in Cab Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-51030 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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