# CVE-2006-0201: Business logic in n/a

> Remote attackers can inject false payment entries into log files via HTTP POST requests to the IPN success script.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/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:** 13 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6xh9-4pw7-5r88

## What is CVE-2006-0201?

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

### Official description

Dave Nielsen and Patrick Breitenbach PayPal Web Services (aka PHP Toolkit) 0.50, and possibly earlier versions, allows remote attackers to enter false payment entries into the log file via HTTP POST requests to ipn_success.php.

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

It affects 1 product.


Products: Paypal Php Toolkit.

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

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

## Is CVE-2006-0201 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0202](https://insights.sbomify.com/CVE-2006-0202/): Information disclosure in n/a (low 3.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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