dbcve.org
Inventory Management SystemApplication · Inventory Management System Project

CVE-2023-4437

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Inventory Management System 1.0. Affected is an unknown function of the file app/ajax/search_sell_paymen_report.php. The manipulation of the argument customer leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-237558 is the identifier 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

Critical SQL injection vulnerability in SourceCodester Inventory Management System 1.0's app/ajax/search_sell_paymen_report.php. The 'customer' parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL commands. This is a classic SQL injection with publicly available exploit code.

MitigationImplement prepared statements/parameterized queries for all database queries involving the customer parameter. Additionally, conduct a full audit of similar files in the application for other SQL injection vulnerabilities.

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
Inventory 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
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 checks

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

  1. Confirm Inventory Management System installation
    Locate the web application root directory and identify if it contains SourceCodester Inventory Management System files. Look for characteristic files like login.php, dashboard files, or the app/ directory structure.
    Affected if The application directory contains SourceCodester Inventory Management System files with an app/ folder structure.
  2. Identify the application version
    Check any version file, README, or meta information in the application root for version number 1.0. Also check the footer or about page of the web interface if accessible.
    Affected if The installed version is exactly 1.0.
  3. Verify the vulnerable file exists
    Check if the file app/ajax/search_sell_paymen_report.php exists in the web application directory. This is the specific file containing the SQL injection vulnerability.
    Affected if The file app/ajax/search_sell_paymen_report.php is present on the server.
  4. Confirm the customer parameter is used
    Open the search_sell_paymen_report.php file and inspect whether the 'customer' parameter is being processed in a database query without proper sanitization or prepared statements.
    Affected if The file contains a database query using the 'customer' parameter without parameterized queries or input sanitization.
  5. Check if the endpoint is accessible
    Attempt to access the URL endpoint app/ajax/search_sell_paymen_report.php via HTTP to confirm it responds. The vulnerability is exploitable remotely through this AJAX endpoint.
    Affected if The AJAX endpoint responds and accepts the customer parameter without authentication or proper input validation.

The environment is affected if running SourceCodester Inventory Management System version 1.0 with the app/ajax/search_sell_paymen_report.php file present and accessible, where the customer parameter is used in unsanitized SQL queries.

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 prepared statements/parameterized queries for all database queries involving the customer parameter. Additionally, conduct a full audit of similar files in the application for other SQL injection vulnerabilities.

Fix this in Inventory Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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