# CVE-2003-0733: Cross-site scripting in n/a

> Remote attackers can execute arbitrary web script and steal credentials via XSS in WebLogic Server and Integration products.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Sep 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cfc9-g2p5-76v2

## What is CVE-2003-0733?

CVE-2003-0733 is a medium-severity cross-site scripting vulnerability in Bea Weblogic Server, published on 4 Sep 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in WebLogic Integration 7.0 and 2.0, Liquid Data 1.1, and WebLogic Server and Express 5.1 through 7.0, allow remote attackers to execute arbitrary web script and steal authentication credentials via (1) a forward instruction to the Servlet container or (2) other vulnerabilities in the WebLogic Server console application.

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

It affects 3 products.


Products: Bea Liquid Data, Bea Weblogic Integration, Bea Weblogic Server.

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

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

## Is CVE-2003-0733 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0733 is a medium-severity cross-site scripting vulnerability in Bea Weblogic Server, published on 4 Sep 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2003-0733 in the wild and no public exploit code.

Affected product: Bea Weblogic Server. 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-0733/ (Markdown: https://insights.sbomify.com/CVE-2003-0733/index.md)
```

## Sources

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

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