# CVE-2004-2139: Code injection in n/a

> Attackers can execute arbitrary code via settings.pl in YaBB Gold, requiring administrative access to the forum.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x2h8-m882-534p

## What is CVE-2004-2139?

CVE-2004-2139 is a high-severity code injection vulnerability in n/a, published on 30 Jun 2005. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unknown vulnerability in Adminedit.pl YaBB 1 Gold before 1.3.2 allows attackers to execute arbitrary code via settings.pl.

## Which versions are affected by CVE-2004-2139?

It affects 1 product.


Products: Yabb Yabb.

## How do I fix CVE-2004-2139?

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

## Is CVE-2004-2139 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3208](https://insights.sbomify.com/CVE-2007-3208/): Other in n/a (critical 10.0)
- [CVE-2004-2403](https://insights.sbomify.com/CVE-2004-2403/): Cross-site request forgery in n/a (critical 10.0)
- [CVE-2004-0343](https://insights.sbomify.com/CVE-2004-0343/): SQL injection in n/a (critical 10.0)
- [CVE-2013-2057](https://insights.sbomify.com/CVE-2013-2057/): Path traversal in YaBB (critical 9.8)
- [CVE-2006-3275](https://insights.sbomify.com/CVE-2006-3275/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2139 and fix it if it is affected.

What it is: CVE-2004-2139 is a high-severity code injection vulnerability in n/a, published on 30 Jun 2005. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2139 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-2004-2139/ (Markdown: https://insights.sbomify.com/CVE-2004-2139/index.md)
```

## Sources

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

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