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

> Remote attackers can inject arbitrary web script into the BEA Tuxedo Administration Console via the INIFILE argument, requiring admin access to exploit.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Nov 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-48ww-7fpq-xhw8

## What is CVE-2003-0623?

CVE-2003-0623 is a medium-severity cross-site scripting vulnerability in Bea Weblogic Server, published on 5 Nov 2003. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in the Administration Console for BEA Tuxedo 8.1 and earlier allows remote attackers to inject arbitrary web script via the INIFILE argument.

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

It affects 2 products.


Products: Bea Tuxedo, Bea Weblogic Server.

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

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

## Is CVE-2003-0623 being exploited?

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

## Other vulnerabilities in Bea Weblogic Server

- [CVE-2007-5576](https://insights.sbomify.com/CVE-2007-5576/): Information disclosure in n/a (medium 6.8)
- [CVE-2003-0621](https://insights.sbomify.com/CVE-2003-0621/): Path traversal in n/a (medium 5.0)
- [CVE-2003-0622](https://insights.sbomify.com/CVE-2003-0622/): Denial of service in n/a (medium 5.0)
- [CVE-2001-1477](https://insights.sbomify.com/CVE-2001-1477/): Missing authorization in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0623 is a medium-severity cross-site scripting vulnerability in Bea Weblogic Server, published on 5 Nov 2003. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2003-0623 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-0623/ (Markdown: https://insights.sbomify.com/CVE-2003-0623/index.md)
```

## Sources

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

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