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

> Remote attackers can execute arbitrary SQL commands via parameters in userscript.php, potentially accessing or modifying database contents.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-57fm-6v8x-57c8

## What is CVE-2006-1930?

CVE-2006-1930 is a medium-severity SQL injection vulnerability in n/a, published on 20 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in userscript.php in Green Minute 1.0 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) huserid, (2) pituus, or (3) date parameters. NOTE: this issue has been disputed by the vendor, saying "those parameters mentioned ARE checked (preg_match) before they are used in SQL-query...  If someone decided to add SQL-injection stuff to certain parameter, they would see an error text, but only because _nothing_ was passed inside that parameter (to MySQL-database)."  As allowed by the vendor, CVE investigated this report on 20060525 and found that the demo site demonstrated a non-sensitive SQL error when given standard SQL injection manipulations

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

It affects 1 product.


Products: Hoito Green Minute.

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

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

## Is CVE-2006-1930 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1930 is a medium-severity SQL injection vulnerability in n/a, published on 20 Apr 2006. 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-2006-1930 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-1930/ (Markdown: https://insights.sbomify.com/CVE-2006-1930/index.md)
```

## Sources

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

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