CVE-2026-86309
Received Received - Intake

SQL Injection in Sales and Inventory System 1.0

Vulnerability report for CVE-2026-86309, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-07

Last updated on: 2026-09-07

Assigner: VulDB

Description

A flaw has been found in itsourcecode Sales and Inventory System 1.0. Impacted is an unknown function of the file /pages/pro_searchfrm.php. This manipulation of the argument ID causes sql injection. The attack can be initiated remotely. The exploit has been published and may be used.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-07
Last Modified
2026-09-07
Generated
2026-09-07
AI Q&A
2026-09-07
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
itsourcecode sales_and_inventory_system 1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a SQL injection flaw in the Sales and Inventory System 1.0. It exists in the file /pages/pro_searchfrm.php where the 'ID' parameter is improperly sanitized before being used in SQL queries. Attackers can inject malicious SQL code via a crafted GET request to manipulate the database.

Detection Guidance
  • Check web server access logs for suspicious GET requests to /pages/pro_searchfrm.php with unusual ID parameters like 'id=1' OR '1'='1'.
  • Use SQL injection detection tools like SQLmap to test the parameter: sqlmap -u "http://target.com/pages/pro_searchfrm.php?id=1" --batch.
  • Monitor database query logs for unexpected or malformed SQL queries originating from the application.
  • Inspect network traffic for repeated requests with varying ID values that may indicate probing attempts.
Impact Analysis

If exploited, this vulnerability allows attackers with valid credentials to access, leak, or tamper with sensitive data in the database. In severe cases, it could lead to full system compromise, including unauthorized administrative access or data deletion.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA due to unauthorized data access or leakage. GDPR requires protecting personal data, while HIPAA mandates safeguarding health information. Exploitation may result in legal penalties, fines, or reputational damage.

Mitigation Strategies
  • Apply input validation to sanitize the 'id' parameter, rejecting non-numeric values or using allowlists.
  • Implement prepared statements with parameter binding for all SQL queries involving user input.
  • Restrict database user permissions to limit potential damage from SQL injection.
  • Update the application code to use modern frameworks that handle input sanitization automatically.
  • Conduct a security audit to identify and fix similar vulnerabilities in other parts of the application.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-86309. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart