# CVE-2005-2805: Business logic in n/a

> Remote attackers can post to non-existent forums by manipulating forum IDs, allowing unauthorized content injection in e107.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **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:** 6 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jrf7-hj59-25w8

## What is CVE-2005-2805?

CVE-2005-2805 is a medium-severity vulnerability in E107 E107, published on 6 Sep 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

forum_post.php in e107 0.6 allows remote attackers to post to non-existent forums by modifying the forum number.

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

It affects 1 product.


Products: E107 E107.

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

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

## Is CVE-2005-2805 being exploited?

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

## Other vulnerabilities in E107 E107

- [CVE-2021-27885](https://insights.sbomify.com/CVE-2021-27885/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-10753](https://insights.sbomify.com/CVE-2016-10753/): Deserialization in n/a (high 8.8)
- [CVE-2018-15901](https://insights.sbomify.com/CVE-2018-15901/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-50916](https://insights.sbomify.com/CVE-2022-50916/): e107 CMS v3.2.1 - Upload restriction bypass (Authenticated [Admin])+ Server file override (high 8.7)
- [CVE-2022-50907](https://insights.sbomify.com/CVE-2022-50907/): e107 CMS v3.2.1 - Admin Upload Restriction Bypass + RCE (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2805 is a medium-severity vulnerability in E107 E107, published on 6 Sep 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2805 in the wild and no public exploit code.

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

## Sources

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

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