# CVE-2004-1893: Missing authorization in n/a

> Remote attackers can access sensitive data and execute SQL commands via an unauthenticated script in Dreamweaver MX when specific testing server options are enabled.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-qw4w-jhg4-f7wc

## What is CVE-2004-1893?

CVE-2004-1893 is a medium-severity missing authorization vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dreamweaver MX, when "Using Driver On Testing Server" or "Using DSN on Testing Server" is selected, uploads the mmhttpdb.asp script to the web site but does not require authentication, which allows remote attackers to obtain sensitive information and possibly execute arbitrary SQL commands via a direct request to mmhttpdb.asp.

## Which versions are affected by CVE-2004-1893?


## How do I fix CVE-2004-1893?

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

## Is CVE-2004-1893 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1893 and fix it if it is affected.

What it is: CVE-2004-1893 is a medium-severity missing authorization vulnerability in n/a, published on 10 May 2005. 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-2004-1893 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-2004-1893/ (Markdown: https://insights.sbomify.com/CVE-2004-1893/index.md)
```

## Sources

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

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