# CVE-2008-1993: File upload in n/a

> Remote attackers can upload arbitrary files via unrestricted FCKEditor access in Acidcat CMS, potentially leading to code execution.

- **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:** 27 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hj8j-8885-9jc3

## What is CVE-2008-1993?

CVE-2008-1993 is a high-severity vulnerability in n/a, published on 27 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Acidcat CMS 3.4.1 does not restrict access to the FCKEditor component, which allows remote attackers to upload arbitrary files.

Weakness: CWE-264

## Which versions are affected by CVE-2008-1993?

It affects 1 product.


Products: Acidcat Acidcat Cms.

## How do I fix CVE-2008-1993?

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

## Is CVE-2008-1993 being exploited?

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

Public exploit code:

- Acidcat CMS 3.4.1 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-0976](https://insights.sbomify.com/CVE-2010-0976/): Missing authorization in n/a (high 7.5)
- [CVE-2008-1990](https://insights.sbomify.com/CVE-2008-1990/): SQL injection in n/a (high 7.5)
- [CVE-2008-1992](https://insights.sbomify.com/CVE-2008-1992/): Missing authorization in n/a (high 7.5)
- [CVE-2010-0984](https://insights.sbomify.com/CVE-2010-0984/): Information disclosure in n/a (medium 5.0)
- [CVE-2008-1991](https://insights.sbomify.com/CVE-2008-1991/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1993 and fix it if it is affected.

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

## Sources

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

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