dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10235

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 flaw has been found in CodeAstro Ingredients Stock Management System 1.0. This vulnerability affects unknown code of the file /Ingredients-Stock/stock_manager.php. This manipulation of the argument txt_search_category causes sql injection. The attack may be initiated remotely. The exploit has been published 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 · moderate confidence

SQL injection vulnerability in CodeAstro Ingredients Stock Management System 1.0. The txt_search_category parameter in /Ingredients-Stock/stock_manager.php is not properly sanitized, allowing attackers to inject malicious SQL queries through this input field.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) for the txt_search_category parameter, and conduct a broader code review to identify and fix similar SQL injection vulnerabilities throughout the application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Verify CodeAstro Ingredients Stock Management System is installed
    Locate the web application root directory and confirm the presence of the Ingredients-Stock folder structure containing stock_manager.php
    Affected if The application directory /Ingredients-Stock/ exists on the server
  2. Confirm the application version
    Check version files, README, or about pages within the CodeAstro application for version 1.0
    Affected if The installed version is 1.0
  3. Verify the vulnerable file exists
    Check for the existence of /Ingredients-Stock/stock_manager.php in the web root
    Affected if The file stock_manager.php exists in the expected path
  4. Inspect the txt_search_category parameter handling
    Review the source code of stock_manager.php and locate the txt_search_category parameter usage in SQL queries
    Affected if The parameter is used in SQL queries without prepared statements or parameterized queries
  5. Confirm the parameter is user-accessible
    Check if the stock_manager.php page is accessible via HTTP and accepts user input through GET or POST requests for txt_search_category
    Affected if The parameter is directly accessible to unauthenticated users

If CodeAstro Ingredients Stock Management System version 1.0 is present with stock_manager.php accessible and the txt_search_category parameter is used in SQL queries without prepared statements, the environment is affected by CVE-2026-10235.

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

Replace dynamic SQL queries with parameterized queries (prepared statements) for the txt_search_category parameter, and conduct a broader code review to identify and fix similar SQL injection vulnerabilities throughout the application.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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