# CVE-2020-14750: Oracle WebLogic Server Remote Code Execution

> Unauthenticated attackers can bypass authentication in the WebLogic Console to take over the server, requiring immediate patching.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2020
- **Updated:** 12 Jan 2026
- **Also known as:** GHSA-9wpc-chhp-343g

## What is CVE-2020-14750?

CVE-2020-14750 is a critical authentication bypass vulnerability in Oracle Weblogic Server, published on 1 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Console). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0 and 14.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

## Which versions are affected by CVE-2020-14750?

It affects 1 product.


Products: Oracle Weblogic Server.

## How do I fix CVE-2020-14750?

No fix has been published for CVE-2020-14750 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-14750 being exploited?

Yes. Attackers have exploited CVE-2020-14750 in the wild since at least 3 Nov 2021.

Public exploit code:

- PoC para las vulnerabilidades CVE-2020-14750 y cve-2020-14882 (github_poc): https://github.com/pprietosanchez/CVE-2020-14750
- Oracle WebLogic Server Administration Console Handle RCE (metasploit)
- https://github.com/kkhacklabs/CVE-2020-14750 (github_poc): https://github.com/kkhacklabs/CVE-2020-14750
- Oracle WebLogic Server - Remote Command Execution (nuclei): http/cves/2020/CVE-2020-14750.yaml

## Other vulnerabilities in Oracle Weblogic Server

- [CVE-2020-14882](https://insights.sbomify.com/CVE-2020-14882/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-14644](https://insights.sbomify.com/CVE-2020-14644/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-2883](https://insights.sbomify.com/CVE-2020-2883/): Oracle WebLogic Server Unspecified (critical 9.8, exploited in the wild)
- [CVE-2020-2551](https://insights.sbomify.com/CVE-2020-2551/): Oracle Fusion Middleware Unspecified (critical 9.8, exploited in the wild)
- [CVE-2018-2628](https://insights.sbomify.com/CVE-2018-2628/): Oracle WebLogic Server Unspecified (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14750 and fix it if it is affected.

What it is: CVE-2020-14750 is a critical authentication bypass vulnerability in Oracle Weblogic Server, published on 1 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-14750 in the wild since at least 3 Nov 2021.

Affected product: Oracle 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-2020-14750/ (Markdown: https://insights.sbomify.com/CVE-2020-14750/index.md)
```

## Sources

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

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