# CVE-2007-2703: Privilege escalation in n/a

> An administrator can corrupt visitor entitlements by providing a long role description, allowing remote authenticated users to access privileged resources.

- **Severity:** Low 3.6 (`AV:N/AC:H/Au:S/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8328-r6wp-frw2

## What is CVE-2007-2703?

CVE-2007-2703 is a low-severity vulnerability in n/a, published on 16 May 2007. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

BEA WebLogic Portal 9.2 GA can corrupt a visitor entitlements role if an administrator provides a long role description, which might allow remote authenticated users to access privileged resources.

## Which versions are affected by CVE-2007-2703?

It affects 1 product.


Products: Oracle Weblogic Portal.

## How do I fix CVE-2007-2703?

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

## Is CVE-2007-2703 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0423](https://insights.sbomify.com/CVE-2006-0423/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2006-0428](https://insights.sbomify.com/CVE-2006-0428/): Missing authorization in n/a (high 7.5)
- [CVE-2007-0426](https://insights.sbomify.com/CVE-2007-0426/): Security feature bypass in n/a (medium 6.8)
- [CVE-2006-1358](https://insights.sbomify.com/CVE-2006-1358/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-0425](https://insights.sbomify.com/CVE-2006-0425/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2703 and fix it if it is affected.

What it is: CVE-2007-2703 is a low-severity vulnerability in n/a, published on 16 May 2007. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2703 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-2007-2703/ (Markdown: https://insights.sbomify.com/CVE-2007-2703/index.md)
```

## Sources

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

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