dbcve.org
Petrol Pump ManagementApplication · Mayurik

CVE-2024-2058

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 was found in SourceCodester Petrol Pump Management Software 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /admin/app/product.php. The manipulation of the argument photo leads to unrestricted upload. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-255373 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 · moderate confidence

SourceCodester Petrol Pump Management Software 1.0 contains an unrestricted file upload vulnerability in /admin/app/product.php. The 'photo' parameter accepts files without proper validation of file type, extension, or content, allowing attackers to upload malicious files (such as PHP web shells) to achieve remote code execution.

MitigationImplement strict whitelist-based file validation for the photo upload functionality, verifying both file extension and MIME type, and storing uploaded files outside the web root or with non-executable extensions.

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 if SourceCodester Petrol Pump Management is installed
    Look for the application in your web server's document root or application directory. The software is typically deployed as a PHP web application.
    Affected if The application SourceCodester Petrol Pump Management (also marketed as Mayurik Petrol Pump Management) is installed on the server.
  2. Verify the installed version is 1.0
    Check the application's version information, typically found in a README file, about page, or version constant in the source code.
    Affected if The installed version is exactly 1.0.
  3. Confirm the vulnerable script exists
    Check if the file /admin/app/product.php exists in the web application directory.
    Affected if The file /admin/app/product.php exists and is accessible via the web server.
  4. Verify the photo upload functionality is accessible
    Check if the admin panel is accessible and the product management feature can be reached. Attempt to access the product.php script directly or log in as an administrator to access the product upload form.
    Affected if The photo upload feature in /admin/app/product.php is accessible and functional.
  5. Inspect the file upload validation
    Review the PHP code in /admin/app/product.php to check if there is any file type, extension, or MIME type validation on the 'photo' parameter before processing uploads.
    Affected if There is no validation or only weak validation (e.g., client-side only, or extension check without content validation) on the 'photo' upload parameter.

A user is affected if they have SourceCodester Petrol Pump Management version 1.0 installed with the /admin/app/product.php script accessible and the photo upload feature lacking proper file validation.

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

Implement strict whitelist-based file validation for the photo upload functionality, verifying both file extension and MIME type, and storing uploaded files outside the web root or with non-executable extensions.

Fix this in Petrol Pump Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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