# CVE-2003-0307: Privilege escalation in n/a

> Remote authenticated users can gain administrative privileges by manipulating the email address field with a pipe separator and admin value.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/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:** 17 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-ppv6-6xg4-x7cw

## What is CVE-2003-0307?

CVE-2003-0307 is a high-severity vulnerability in n/a, published on 17 May 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Poster version.two allows remote authenticated users to gain administrative privileges by appending the "|" field separator and an "admin" value into the email address field.

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

It affects 1 product.


Products: Poster Poster.

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

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

## Is CVE-2003-0307 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0307 is a high-severity vulnerability in n/a, published on 17 May 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0307 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-2003-0307/ (Markdown: https://insights.sbomify.com/CVE-2003-0307/index.md)
```

## Sources

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

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