dbcve.org
Petrol Pump ManagementApplication · Mayurik

CVE-2024-10407

HIGH · 7.2 CVSS v3.1 Published 2024-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 vulnerability, which was classified as critical, was found in SourceCodester Petrol Pump Management Software 1.0. This affects an unknown part of the file /admin/edit_customer.php. The manipulation of the argument id leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

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 SourceCodester Petrol Pump Management Software 1.0 allows remote attackers to inject malicious SQL queries via the 'id' parameter in /admin/edit_customer.php. The application fails to properly sanitize or use parameterized queries when handling user input, enabling attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in edit_customer.php. Apply input validation on the id parameter and enforce least privilege on the database user account.

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
Petrol Pump ManagementApplication
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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

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

  1. Confirm product installation
    Locate the SourceCodester or Mayurik Petrol Pump Management Software installation directory. Look for the main application files or check web server document roots for this application.
    Affected if The application is installed and accessible via web server
  2. Verify software version
    Check the application's version information, typically found in a README file, about page, or version constant in source code files. Compare against version 1.0.
    Affected if The installed version is exactly 1.0 (Mayurik Petrol Pump Management)
  3. Locate vulnerable file
    Check for the presence of /admin/edit_customer.php in the web application directory. This file should exist in the application's admin folder.
    Affected if The file /admin/edit_customer.php exists in the application
  4. Check id parameter handling
    Inspect the edit_customer.php source code and locate the code that handles the 'id' parameter. Look for direct insertion of the id parameter into SQL queries without using prepared statements or parameterized queries.
    Affected if The id parameter is used in SQL queries without parameterized queries or proper input sanitization

The environment is affected if the Mayurik Petrol Pump Management version 1.0 is installed, the /admin/edit_customer.php file exists, and the id parameter in that file is processed in SQL queries without parameterized queries or 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in edit_customer.php. Apply input validation on the id parameter and enforce least privilege on the database user account.

Recommended fix Moderate confidence
  1. 1. Locate the file /admin/edit_customer.php in the application root directory.
  2. 2. Identify the SQL query that uses the 'id' parameter without proper sanitization.
  3. 3. Replace the vulnerable SQL query with a parameterized query (prepared statement). For example, change from: $sql = "SELECT * FROM customers WHERE id = " . $_GET['id']; to use mysqli_prepare() or PDO with bound parameters.
  4. 4. Alternatively, if using mysqli, implement: $stmt = $mysqli->prepare("SELECT * FROM customers WHERE id = ?"); $stmt->bind_param("i", $id); where $id is sanitized integer.
  5. 5. Add input validation: ensure the 'id' parameter is a valid integer using intval() or is_numeric() before using it in queries.
  6. 6. Apply the same SQL injection protections to all other files that accept user input in the /admin/ directory.
  7. 7. Test the fix by attempting the original SQL injection payload to confirm it is blocked.
  8. 8. Restart the web server if necessary to apply changes.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Petrol Pump Management Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10407 — 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-10407 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