# CVE-2005-2633: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via the absolutepath parameter in multiple admin scripts of PHPTB Topic Board.

- **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:** 20 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jr6j-q72x-3jfr

## What is CVE-2005-2633?

CVE-2005-2633 is a high-severity code injection vulnerability in n/a, published on 20 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple PHP file inclusion vulnerabilities in (1) admin_o.php, (2) board_o.php, (3) dev_o.php, (4) file_o.php or (5) tech_o.php in PHPTB Topic Board 2.0 and earlier allow remote attackers to execute arbitrary PHP code via the absolutepath parameter.

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

It affects 1 product.


Products: Phptb Topic Boards.

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

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

## Is CVE-2005-2633 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2633 exists.

Public exploit code:

- PHPTB Topic Board 2.0 - 'admin_o.php?absolutepath' Remote File Inclusion (exploitdb)
- PHPTB Topic Board 2.0 - 'board_o.php?absolutepath' Remote File Inclusion (exploitdb)
- PHPTB Topic Board 2.0 - 'dev_o.php?absolutepath' Remote File Inclusion (exploitdb)
- PHPTB Topic Board 2.0 - 'file_o.php?absolutepath' Remote File Inclusion (exploitdb)
- PHPTB Topic Board 2.0 - 'tech_o.php?absolutepath' Remote File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-2587](https://insights.sbomify.com/CVE-2005-2587/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2633 is a high-severity code injection vulnerability in n/a, published on 20 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2633 exists.

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-2633/ (Markdown: https://insights.sbomify.com/CVE-2005-2633/index.md)
```

## Sources

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

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