# CVE-2006-6927: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via multiple input fields in the Rialto web application, potentially compromising data integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A: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 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wmx2-pcfq-92qg

## What is CVE-2006-6927?

CVE-2006-6927 is a high-severity SQL injection vulnerability in n/a, published on 13 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in Rialto 1.6 allow remote attackers to execute arbitrary SQL commands via (1) the uname (username) and (2) pword (passwd) fields in (a) admin/default.asp; the (3) ID parameter to (b) listfull.asp or (c) printmain.asp; the (4) cat parameter to (d) listmain.asp, (e) searchoption.asp, or (f) searchmain.asp; the (5) Keyword parameter to (g) searchkey.asp; the (6) area parameter to searchmain.asp or searchoption.asp; the (7) searchin parameter to searchkey.asp; or the (8) cost1, (9) cost2, (10) acreage1, or (11) squarefeet1 parameters to searchoption.asp.  NOTE: some of these details are obtained from third party information.

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

It affects 1 product.


Products: Grandora Rialto.

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

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

## Is CVE-2006-6927 being exploited?

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

Public exploit code:

- Grandora Rialto 1.6 - '/admin/default.asp' Multiple SQL Injections (exploitdb)
- Grandora Rialto 1.6 - 'listfull.asp?ID' SQL Injection (exploitdb)
- Grandora Rialto 1.6 - 'listmain.asp?cat' SQL Injection (exploitdb)
- Grandora Rialto 1.6 - 'printmain.asp?ID' SQL Injection (exploitdb)
- Grandora Rialto 1.6 - 'searchkey.asp' Multiple SQL Injections (exploitdb)
- Grandora Rialto 1.6 - 'searchmain.asp' Multiple SQL Injections (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6928](https://insights.sbomify.com/CVE-2006-6928/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6927 is a high-severity SQL injection vulnerability in n/a, published on 13 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6927 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-2006-6927/ (Markdown: https://insights.sbomify.com/CVE-2006-6927/index.md)
```

## Sources

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

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