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

> Authenticated attackers can inject SQL via search parameters to steal usernames and passwords in PHP Ticket.

- **Severity:** Medium 6.5 (`AV:N/AC:L/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:** 29 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-94q2-wr5w-xm3h

## What is CVE-2006-1481?

CVE-2006-1481 is a medium-severity SQL injection vulnerability in n/a, published on 29 Mar 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in search.php in PHP Ticket 0.71 allows remote authenticated users to execute arbitrary SQL commands and obtain usernames and passwords via the frm_search_in parameter.

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

It affects 1 product.


Products: Php Ticket Php Ticket.

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

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

## Is CVE-2006-1481 being exploited?

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

Public exploit code:

- PHP Ticket 0.71 - 'search.php' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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