CVE-2026-11495
Received Received - Intake
SQL Injection in CodeAstro Ingredients Stock Management System

Publication date: 2026-06-08

Last updated on: 2026-06-08

Assigner: VulDB

Description
A vulnerability was detected in CodeAstro Ingredients Stock Management System 1.0. This impacts an unknown function of the file /Ingredients-Stock/add_stock.php. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit is now public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-08
Last Modified
2026-06-08
Generated
2026-06-08
AI Q&A
2026-06-08
EPSS Evaluated
N/A
NVD
CVE-2026-11495
EUVD
EUVD-2026-35026
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
codeastro ingredients_stock_management_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
Compliance Impact

The SQL injection vulnerability in CodeAstro Ingredients Stock Management System 1.0 can lead to unauthorized database access, data tampering, and sensitive information leakage. Such impacts can compromise the confidentiality and integrity of personal or sensitive data stored within the system.

This type of vulnerability may result in non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal data and sensitive health information against unauthorized access and breaches.

Failure to mitigate this vulnerability could expose organizations to regulatory penalties, legal liabilities, and reputational damage due to potential data breaches.

Executive Summary

The CVE-2026-11495 vulnerability is a SQL injection flaw found in the Ingredients Stock Management System version 1.0, specifically in the file /Ingredients-Stock/add_stock.php.

The vulnerability occurs due to improper input validation of the 'id' parameter, which allows attackers to inject malicious SQL queries.

This flaw enables attackers to execute arbitrary SQL commands remotely, potentially leading to unauthorized database access and data manipulation.

Impact Analysis

Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to tamper with data or extract sensitive information.

It may also result in a full system compromise if attackers leverage the SQL injection to execute further malicious actions.

Detection Guidance

This vulnerability can be detected by testing the 'id' parameter in the /Ingredients-Stock/add_stock.php file for SQL injection flaws. A common method is to use time-based blind SQL injection payloads to observe if the system response time changes, indicating vulnerability.

  • Use tools like sqlmap or manual curl commands with payloads to test the 'id' parameter.
  • Example curl command to test for time-based blind SQL injection: curl -G 'http://target/Ingredients-Stock/add_stock.php' --data-urlencode "id=1' AND IF(SLEEP(5),1,0)-- "
  • Monitor response delays to confirm if the injection is successful.
Mitigation Strategies

Immediate mitigation steps include implementing prepared statements to handle database queries safely and applying strict input validation on the 'id' parameter to prevent malicious input.

  • Use prepared statements or parameterized queries instead of directly embedding user input in SQL queries.
  • Validate and sanitize all inputs, especially the 'id' parameter, to ensure only expected data types and values are accepted.
  • Minimize database user permissions to limit the impact of a potential exploit.
  • Conduct regular security audits and code reviews to detect and fix similar vulnerabilities.
Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-11495. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart