# CVE-2026-6163: code-projects Lost and Found Thing Management catageory.php sql injection

> Remote attackers can exploit SQL injection in the category parameter to read or modify database contents in the Lost and Found Thing Management application.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-6vp8-f7xg-8xgc

## What is CVE-2026-6163?

CVE-2026-6163 is a medium-severity SQL injection vulnerability in code-projects Lost and Found Thing Management, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in code-projects Lost and Found Thing Management 1.0. Affected by this issue is some unknown functionality of the file /catageory.php. Such manipulation of the argument cat leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-6163 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6163 is a medium-severity SQL injection vulnerability in code-projects Lost and Found Thing Management, published on 13 Apr 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-6163 in the wild and no public exploit code.

Affected product: code-projects Lost and Found Thing Management. 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-6163/ (Markdown: https://insights.sbomify.com/CVE-2026-6163/index.md)
```

## Sources

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

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