# CVE-2005-0267: Privilege escalation in n/a

> Remote attackers can create administrator accounts in FlatNuke by injecting carriage returns into the avatar URL field, leading to full system compromise.

- **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:** 10 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-chh7-246w-c444

## What is CVE-2005-0267?

CVE-2005-0267 is a high-severity vulnerability in n/a, published on 10 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

index.php in FlatNuke 2.5.1 allows remote attackers to create an administrator account via carriage returns and #10 in the url_avatar field, which is interpreted as a sensitive directive.

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

It affects 1 product.


Products: Flatnuke Flatnuke.

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

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

## Is CVE-2005-0267 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4448](https://insights.sbomify.com/CVE-2005-4448/): Auth bypass in n/a (critical 10.0)
- [CVE-2005-1894](https://insights.sbomify.com/CVE-2005-1894/): Code injection in n/a (high 7.5)
- [CVE-2005-0268](https://insights.sbomify.com/CVE-2005-0268/): Code injection in n/a (high 7.5)
- [CVE-2005-2815](https://insights.sbomify.com/CVE-2005-2815/): Denial of service in n/a (medium 6.4)
- [CVE-2005-1892](https://insights.sbomify.com/CVE-2005-1892/): Information disclosure in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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