# CVE-2005-1031: File upload in n/a

> Remote attackers can upload arbitrary files to execute code if custom avatar uploads are enabled in RUNCMS.

- **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:** 9 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6h83-jc39-4w5p

## What is CVE-2005-1031?

CVE-2005-1031 is a medium-severity vulnerability in n/a, published on 9 Apr 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RUNCMS 1.1A, and possibly other products based on e-Xoops (exoops), when "Allow custom avatar upload" is enabled, does not properly verify uploaded files, which allows remote attackers to upload arbitrary files.

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

It affects 2 products.


Products: E-Xoops E-Xoops, Runcms Runcms.

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

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

## Is CVE-2005-1031 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6380](https://insights.sbomify.com/CVE-2007-6380/): SQL injection in n/a (high 7.5)
- [CVE-2005-0911](https://insights.sbomify.com/CVE-2005-0911/): SQL injection in n/a (high 7.5)
- [CVE-2005-0910](https://insights.sbomify.com/CVE-2005-0910/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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