dbcve.org
Petrol Pump ManagementApplication · Mayurik

CVE-2024-2062

HIGH · 7.2 CVSS v3.1 Published 2024-03-01
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, has been found in SourceCodester Petrol Pump Management Software 1.0. This issue affects some unknown processing of the file /admin/edit_categories.php. The manipulation of the argument id leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-255377 was assigned to this vulnerability.

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 commands through the 'id' parameter in /admin/edit_categories.php. The lack of proper input sanitization enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries, implement strict input validation on the id parameter, and apply principle of least privilege to database accounts.

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. Identify the installed application version
    Locate version information in the application files, typically in a readme.txt, version.php, or the main index file header. Check the source code for a version constant or check the application footer for version display.
    Affected if The installed version is Mayurik Petrol Pump Management 1.0 (exact match)
  2. Confirm the vulnerable file exists
    Check for the presence of /admin/edit_categories.php in the web root directory of the application.
    Affected if The file /admin/edit_categories.php exists in the application directory
  3. Verify the id parameter is used
    Open /admin/edit_categories.php and search for code that uses the 'id' parameter directly in SQL queries without apparent sanitization, parameter binding, or prepared statements.
    Affected if The file contains SQL queries that directly incorporate the 'id' parameter without input validation or parameterized queries
  4. Check if admin interface is accessible
    Attempt to access /admin/edit_categories.php via HTTP request or verify the admin panel is accessible without authentication restrictions.
    Affected if The admin interface containing edit_categories.php is reachable (authentication may be required but is not a mitigation for the SQL injection)
  5. Review database query implementation
    Examine the PHP code in edit_categories.php to identify all SQL query constructions that involve the 'id' parameter. Look for patterns like $_GET['id'] or $_POST['id'] being concatenated into SQL strings.
    Affected if SQL queries in the file directly concatenate or interpolate the 'id' parameter without using prepared statements or escaping functions

You are affected if you are running Mayurik Petrol Pump Management version 1.0 and the file /admin/edit_categories.php exists with unprotected SQL queries using the 'id' parameter.

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 prepared statements/parameterized queries, implement strict input validation on the id parameter, and apply principle of least privilege to database accounts.

Fix this in Petrol Pump Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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