# CVE-2009-4595: SQL injection in n/a

> Remote authenticated users can execute arbitrary SQL commands via the sup_id parameter in PHP Inventory.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-jw3g-x4rr-j3x2

## What is CVE-2009-4595?

CVE-2009-4595 is a medium-severity SQL injection vulnerability in n/a, published on 12 Jan 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in index.php in PHP Inventory 1.2 allows remote authenticated users to execute arbitrary SQL commands via the sup_id parameter in a suppliers details action.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

## Which versions are affected by CVE-2009-4595?

It affects 1 product.


Products: Phpwares Php Inventory.

## How do I fix CVE-2009-4595?

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

## Is CVE-2009-4595 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4595 exists.

Public exploit code:

- PHP Inventory 1.2 - Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-4597](https://insights.sbomify.com/CVE-2009-4597/): SQL injection in n/a (high 7.5)
- [CVE-2009-4596](https://insights.sbomify.com/CVE-2009-4596/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4595 and fix it if it is affected.

What it is: CVE-2009-4595 is a medium-severity SQL injection vulnerability in n/a, published on 12 Jan 2010. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4595 exists.

Affected product: n/a. 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-2009-4595/ (Markdown: https://insights.sbomify.com/CVE-2009-4595/index.md)
```

## Sources

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

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