dbcve.org
Supply Chain ManagementApplication · Anisha

CVE-2024-9322

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-29
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 was found in code-projects Supply Chain Management 1.0. It has been classified as critical. Affected is an unknown function of the file /admin/edit_manufacturer.php. The manipulation of the argument id leads to sql injection. It is possible to launch 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

A SQL injection vulnerability exists in the code-projects Supply Chain Management 1.0 application at /admin/edit_manufacturer.php. The 'id' parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. The 9.8 CVSS score indicates this is a critical severity issue with no authentication requirement mentioned.

MitigationImplement parameterized queries (prepared statements) for all database operations involving the 'id' parameter in edit_manufacturer.php, add input validation and output encoding, and restrict access to the admin panel. Consider applying a web application firewall rule as a temporary mitigation while the code fix is developed.

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
Supply Chain 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
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. Identify if code-projects Supply Chain Management 1.0 is installed
    Search the web root directory for files named 'edit_manufacturer.php' or look for directory containing 'Supply Chain Management' or similar naming. Common paths may include /var/www/html/, /www/, or C:\inetpub\wwwroot\
    Affected if The application is code-projects Supply Chain Management version 1.0 located on the server
  2. Verify the application version
    Check for version indicators such as a version.php file, footer copyright text in the application, or a README/install file that lists version 1.0
    Affected if The installed version is exactly 1.0 (Anisha Supply Chain Management)
  3. Confirm the vulnerable file exists
    Locate the file /admin/edit_manufacturer.php within the application directory and verify it exists
    Affected if The file edit_manufacturer.php exists in the /admin/ directory of the application
  4. Check if the id parameter is handled unsafely
    Examine the source code of edit_manufacturer.php and look for SQL queries that directly use the 'id' parameter without parameterized queries or proper sanitization (e.g., direct insertion of $_GET['id'] or $_POST['id'] into SQL strings)
    Affected if The code contains unsanitized SQL queries using the 'id' parameter (e.g., SELECT * FROM table WHERE id='$_GET[id]')
  5. Determine if the admin endpoint is exposed
    Attempt to access the /admin/ path or check server access logs for requests to edit_manufacturer.php
    Affected if The /admin/ interface is accessible without authentication

If the system runs Anisha Supply Chain Management version 1.0 with the vulnerable edit_manufacturer.php file present and accessible, and the 'id' parameter is used in SQL queries without sanitization or prepared statements, the environment is affected by CVE-2024-9322.

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 parameterized queries (prepared statements) for all database operations involving the 'id' parameter in edit_manufacturer.php, add input validation and output encoding, and restrict access to the admin panel. Consider applying a web application firewall rule as a temporary mitigation while the code fix is developed.

Fix this in Supply Chain Management 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-2024-9322 — 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-9322 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