# CVE-2026-71207: SQL injection in Stock-Inventory-Management-System

> Unauthenticated attackers can bypass authentication via SQL injection or hardcoded credentials in login.php, gaining full administrative access to the inventory system.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-8924-6725-h379

## What is CVE-2026-71207?

CVE-2026-71207 is a critical SQL injection vulnerability in mrswapnilsahu Stock-Inventory-Management-System, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Stock-Inventory-Management-System application's login.php assigns raw username/password values to and builds its authentication query by directly concatenating those session values into a SQL statement with no parameterization or escaping. The same script additionally contains hardcoded administrative credentials (admin/neola) in a post-login conditional check, providing a second, independent full-authentication-bypass path.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-71207?


## How do I fix CVE-2026-71207?

No fix has been published for CVE-2026-71207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71207 being exploited?

There is no known exploitation of CVE-2026-71207 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71207 and fix it if it is affected.

What it is: CVE-2026-71207 is a critical SQL injection vulnerability in mrswapnilsahu Stock-Inventory-Management-System, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71207 in the wild and no public exploit code.

Affected product: mrswapnilsahu Stock-Inventory-Management-System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71207/ (Markdown: https://insights.sbomify.com/CVE-2026-71207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71207
- OSV: https://osv.dev/vulnerability/CVE-2026-71207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71207/
Summaries are generated and may contain mistakes; the official description above is the record.