# CVE-2006-2349: File upload in n/a

> Remote attackers can upload arbitrary files to execute code or perform XSS attacks via unprotected HTML editor endpoints.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 12 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7h53-8jvg-g82x

## What is CVE-2006-2349?

CVE-2006-2349 is a medium-severity vulnerability in n/a, published on 12 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

E-Business Designer (eBD) 3.1.4 and earlier allows remote attackers to upload or modify arbitrary files, and execute arbitrary code, via a direct request to (1) common/html_editor/image_browser.upload.html, (2) common/html_editor/image_browser.html, or (3) common/html_editor/html_editor.html.  NOTE: this can also be used for cross-site scripting (XSS) attacks by uploading cascading style sheet (.CSS) files.

## Which versions are affected by CVE-2006-2349?

It affects 1 product.


Products: Oasyssoft E-Business Designer.

## How do I fix CVE-2006-2349?

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

## Is CVE-2006-2349 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2347](https://insights.sbomify.com/CVE-2006-2347/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-2348](https://insights.sbomify.com/CVE-2006-2348/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2349 and fix it if it is affected.

What it is: CVE-2006-2349 is a medium-severity vulnerability in n/a, published on 12 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2349 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-2006-2349/ (Markdown: https://insights.sbomify.com/CVE-2006-2349/index.md)
```

## Sources

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

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