# CVE-2003-1466: Server-side request forgery in n/a

> Remote attackers can use Phorum as a connection proxy to other sites via register or login scripts, enabling server-side request forgery.

- **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:** 24 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-r232-rpm5-4rvw

## What is CVE-2003-1466?

CVE-2003-1466 is a high-severity server-side request forgery vulnerability in Phorum Phorum, published on 24 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in Phorum 3.4 through 3.4.2 allows remote attackers to use Phorum as a connection proxy to other sites via (1) register.php or (2) login.php.

## Which versions are affected by CVE-2003-1466?

It affects 1 product.


Products: Phorum Phorum.

## How do I fix CVE-2003-1466?

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

## Is CVE-2003-1466 being exploited?

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

## Other vulnerabilities in Phorum Phorum

- [CVE-2003-1487](https://insights.sbomify.com/CVE-2003-1487/): Command injection in n/a (critical 10.0)
- [CVE-2007-2338](https://insights.sbomify.com/CVE-2007-2338/): Cross-site request forgery in n/a (high 7.5)
- [CVE-2007-2339](https://insights.sbomify.com/CVE-2007-2339/): SQL injection in n/a (high 7.5)
- [CVE-2006-6550](https://insights.sbomify.com/CVE-2006-6550/): Code injection in n/a (high 7.5)
- [CVE-2006-3249](https://insights.sbomify.com/CVE-2006-3249/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1466 and fix it if it is affected.

What it is: CVE-2003-1466 is a high-severity server-side request forgery vulnerability in Phorum Phorum, published on 24 Oct 2007. 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-2003-1466 in the wild and no public exploit code.

Affected product: Phorum Phorum. 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-2003-1466/ (Markdown: https://insights.sbomify.com/CVE-2003-1466/index.md)
```

## Sources

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

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