# CVE-2005-3201: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands in Utopia News Pro via the newsid parameter when specific PHP configurations are enabled.

- **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:** 14 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mh98-9c79-r68x

## What is CVE-2005-3201?

CVE-2005-3201 is a high-severity SQL injection vulnerability in n/a, published on 14 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in news.php for Utopia News Pro (UNP) 1.1.3, when magic_quotes_gpc is disabled and register_globals is enabled, allows remote attackers to execute arbitrary SQL via the newsid parameter.

## Which versions are affected by CVE-2005-3201?


## How do I fix CVE-2005-3201?

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

## Is CVE-2005-3201 being exploited?

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

Public exploit code:

- Utopia News Pro 1.1.3 - 'news.php' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3201 and fix it if it is affected.

What it is: CVE-2005-3201 is a high-severity SQL injection vulnerability in n/a, published on 14 Oct 2005. 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-2005-3201 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-2005-3201/ (Markdown: https://insights.sbomify.com/CVE-2005-3201/index.md)
```

## Sources

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

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