# CVE-2006-7161: SQL injection vulnerability in giris_yap.asp in Hazir Site 2.0 allows remote attackers to bypass authentication via the (1) k_a class or (2) sifre parameter.


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fhw4-v23g-fm4r

## What is CVE-2006-7161?

CVE-2006-7161 is a high-severity vulnerability in n/a, published on 7 Mar 2007. 

### Official description

SQL injection vulnerability in giris_yap.asp in Hazir Site 2.0 allows remote attackers to bypass authentication via the (1) k_a class or (2) sifre parameter.

## Which versions are affected by CVE-2006-7161?

It affects 1 product.


Products: Aspindir Hazirsite.

## How do I fix CVE-2006-7161?

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

## Is CVE-2006-7161 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7161 and fix it if it is affected.

What it is: CVE-2006-7161 is a high-severity vulnerability in n/a, published on 7 Mar 2007. 
Exploitation: There is no known exploitation of CVE-2006-7161 in the wild and no public exploit code.

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-2006-7161/ (Markdown: https://insights.sbomify.com/CVE-2006-7161/index.md)
```

## Sources

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

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