How severe is CVE-2020-2551?

CVE-2020-2551 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2020-2551?

CVE-2020-2551 affects the following products: oracle weblogic server.

How do I patch CVE-2020-2551?

No patch has shipped for CVE-2020-2551 yet — track the oracle weblogic server advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2020-2551 across my infrastructure?

Inventory every oracle weblogic server deployment and check each version against the affected-products list above.

How do I mitigate CVE-2020-2551 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2020-2551 actively exploited in the wild?

Yes. There are 20 known exploit references for CVE-2020-2551, including 13 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-2551?

CVE-2020-2551 has an EPSS (Exploit Prediction Scoring System) score of 92.8%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2020-2551 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2020-2551 (Oracle Fusion Middleware Unspecified Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-11-16. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-12-07. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Which products and versions are affected by CVE-2020-2551?

CVE-2020-2551 affects oracle weblogic server (4 versions, e.g. 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0…). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2020-2551?

A Nuclei detection template exists for CVE-2020-2551, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-2551 published, and has it been updated?

CVE-2020-2551 was published on January 15, 2020 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2020-2551 — Weblogic Server

CRITICAL

CVE-2020-2551 is a critical-severity (CVSS 9.8) vulnerability in oracle weblogic server. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-11-16) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: WLS Core Components). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0…

Published

Jan 15, 2020

Updated

Jun 17, 2026

Affected

1 product

Patched

See advisory

Exploits

20 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-11-16. Federal agencies were required to remediate by 2023-12-07.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2020-2551.

EPSS Exploitation Probability

via FIRST.org ↗

92.8%probability of exploitation in next 30 days

Very High Risk-0.40%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-2551 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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

Affected Products

1 product · 4 configurations

Application

weblogic serveroracle

4 versions

10.3.6.0.012.1.3.0.012.2.1.3.012.2.1.4.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.