dbcve.org
Inventory Management SystemApplication · Code Projects

CVE-2025-6665

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-25
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
Public exploit 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 has been found in code-projects Inventory Management System 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /php_action/editBrand.php. The manipulation of the argument editBrandStatus leads to sql injection. The attack can be launched 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 the code-projects Inventory Management System 1.0 allows remote attackers to inject arbitrary SQL commands via the editBrandStatus parameter in /php_action/editBrand.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries, implement strict input validation on all user-supplied parameters, and apply the vendor patch when available. Restrict database account permissions to minimum required.

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 Code Projects Inventory Management System is installed
    Locate the application installation directory. Look for the Inventory Management System by Code Projects - typically deployed on a web server. Identify the installation path.
    Affected if The Code Projects Inventory Management System application is present on the system
  2. Verify the application version is 1.0
    Check version metadata in the application. Look for a version file, README, or check the main index page for version information. Compare against the affected version range.
    Affected if The installed version is exactly 1.0
  3. Locate the vulnerable PHP file
    Search for the file /php_action/editBrand.php within the web application directory structure. Verify this file exists in the installation.
    Affected if The file /php_action/editBrand.php exists in the application
  4. Confirm editBrandStatus parameter exposure
    Check if the application is accessible over HTTP/HTTPS and the editBrandStatus parameter is processed by editBrand.php. This endpoint accepts user input.
    Affected if The editBrandStatus parameter in editBrand.php is accessible and processes user input without sanitization

A system is affected if Code Projects Inventory Management System version 1.0 is installed with the vulnerable /php_action/editBrand.php file accessible, as the editBrandStatus parameter accepts unsanitized input.

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 prepared statements/parameterized queries, implement strict input validation on all user-supplied parameters, and apply the vendor patch when available. Restrict database account permissions to minimum required.

Recommended fix Moderate confidence
  1. 1. Locate the vulnerable file /php_action/editBrand.php in your codebase
  2. 2. Identify the line(s) where the editBrandStatus parameter is used in the SQL query without proper parameterization
  3. 3. Replace any direct string concatenation of the editBrandStatus parameter with prepared statements (PDO or MySQLi with parameterized queries)
  4. 4. Example fix: Use $stmt = $db->prepare('UPDATE brands SET status = ? WHERE id = ?'); followed by $stmt->bind_param('si', $editBrandStatus, $brandId);
  5. 5. After applying the fix, test the editBrand functionality to ensure it still works correctly
  6. 6. Deploy the patched file to your production environment
Caveat This is a patch to the existing code; no version upgrade is available for this open-source project

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

Fix this in Inventory Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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