/

CVE-2026-87925

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in inventory-management-system

CVE-2026-87925

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Unauthorized database access, data manipulation, and potential application compromise

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A remotely exploitable SQL injection vulnerability affects the storeCustomerOrderInvoice function in includes/manage.php of the inventory-management-system.

By manipulating the pro_name[] parameter, an attacker may influence database queries, potentially accessing, modifying, or disrupting application data. Public exploit information is reportedly available, increasing the likelihood of active abuse.

Affected context

The vulnerability occurs in deployments of the inventory-management-system that expose the order invoice functionality and construct database queries using values derived from the pro_name[] parameter. Risk is greatest where the affected endpoint is reachable remotely and request parameters are not safely separated from SQL statements through parameterized database access.

Exploit preconditions

  • Attack surface: Remotely accessible web functionality in includes/manage.php
  • Required access: The ability to send requests to the affected order invoice operation; authentication requirements may depend on deployment configuration
  • Trigger point: Processing of the pro_name[] request parameter by storeCustomerOrderInvoice
  • Why exploitation is possible: User-controlled input may influence SQL query construction without sufficient parameterization or equivalent separation between data and query logic

Why this happens

The underlying issue is a failure to treat request data as strictly data when constructing or executing database queries. This behavior maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection). The related CWE-74 classification reflects the broader injection pattern, in which attacker-controlled input is interpreted as part of a command or expression rather than being safely bound as a value.

Potential impact

  • An attacker may read sensitive records from the application database.
  • An attacker could alter or delete business data.
  • The vulnerability may enable unauthorized access to customer or order information.
  • Database availability could be disrupted through abusive queries.
  • In some deployments, broader application compromise could occur if database privileges are excessive.

General mitigation guidance

Mitigation generally focuses on removing the connection between untrusted input and executable SQL syntax.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for all database operations.
  • Treat array parameters such as pro_name[] as untrusted and validate their type, structure, length, and allowed values.
  • Apply server-side allowlists and schema validation before database processing.
  • Avoid dynamically concatenating request values into SQL statements.
  • Run the application with a database account limited to the operations it requires.
  • Protect administrative or order-management functions with appropriate authentication and authorization controls.
  • Use secure-by-default data-access abstractions that separate query construction from parameter values.

How teams detect issues like this

Organizations can look for SQL injection risks through:

  • Static analysis rules identifying string concatenation or interpolation in SQL construction.
  • Code review checks for request parameters reaching database APIs without parameter binding.
  • Tests that submit unexpected types, lengths, and special characters to array and scalar parameters.
  • Web application firewall or API policy rules monitoring suspicious query-oriented input patterns.
  • Database audit logs showing unusual query errors, enumeration behavior, or access outside normal application workflows.
  • Automated security review tools that trace user-controlled data into query execution paths.

Sources

SourceLink
github.comgithub.com/Rizwan17/inventory-management-system/
github.comgithub.com/Rizwan17/inventory-management-system/issues/13
vuldb.comvuldb.com/cve/CVE-2026-87925
vuldb.comvuldb.com/submit/911138
vuldb.comvuldb.com/vuln/401812
vuldb.comvuldb.com/vuln/401812/cti

Frequently asked

questions

Yes. The reported attack surface is a web-accessible function, and exploitation may be possible by sending manipulated input to the pro_name[] parameter. The exact scope depends on routing, authentication, and deployment controls.

Not necessarily. The required access depends on whether the affected order invoice operation is publicly reachable or protected by authentication and authorization. Any exposed endpoint should be treated as potentially at risk until its access requirements are confirmed.

Use parameterized queries or prepared statements, validate the expected array structure and values, and ensure request data is never concatenated into SQL syntax.

Combine secure database APIs with least-privilege database accounts, server-side input validation, authorization checks, code review, automated analysis, and monitoring for anomalous database activity.

Find out what's already
exploitable in your codebase.