# CVE-2003-0731: Privilege escalation in n/a

> A guest user can gain administrative privileges by sending a crafted POST request to the authentication servlet in CiscoWorks CMF.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 4 Sep 2003
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vccp-g983-v87h

## What is CVE-2003-0731?

CVE-2003-0731 is a critical vulnerability in n/a, published on 4 Sep 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CiscoWorks Common Management Foundation (CMF) 2.1 and earlier allows the guest user to gain administrative privileges via a certain POST request to com.cisco.nm.cmf.servlet.CsAuthServlet, possibly involving the "cmd" parameter with a modifyUser value and a modified "priviledges" parameter.

## Which versions are affected by CVE-2003-0731?

It affects 4 products.


Products: Cisco Ciscoworks Cd1, Cisco Ciscoworks Common Management Foundation, Cisco Resource Manager, Cisco Resource Manager Essentials.

## How do I fix CVE-2003-0731?

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

## Is CVE-2003-0731 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0732](https://insights.sbomify.com/CVE-2003-0732/): Privilege escalation in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0731 and fix it if it is affected.

What it is: CVE-2003-0731 is a critical vulnerability in n/a, published on 4 Sep 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0731 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-2003-0731/ (Markdown: https://insights.sbomify.com/CVE-2003-0731/index.md)
```

## Sources

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

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