Skip to content
vulnerability

CVE-2020-2883

9.8
Critical
KEV · Exploited in wildEPSS 95%Patch available

Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Core). 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, T3 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).

exploited
Yes, in CISA KEV since 7 Jan 2025fix by 28 Jan 2025 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 94.6%
Published 15 Apr 2020Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

triage
surface unknownruntimeWAF can block: partlyAV · network

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2020-2883 being exploited?

Yes. CVE-2020-2883 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2020-2883?

CVE-2020-2883 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2020-2883?

Yes. A fix has been recorded for CVE-2020-2883. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2020-2883 affect?

CVE-2020-2883 affects oracle:weblogic_server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
oracle:weblogic_server
affected versions
Oracle Corporation WebLogic Server
  • affected10.3.6.0.0
  • affected12.1.3.0.0
  • affected12.2.1.3.0
  • affected12.2.1.4.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Public exploit code: 1 Metasploit module · 7 GitHub proofs of concept · 1 Nuclei template

Nuclei
GitHub proofs of concept
+3 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 11 Jan 2025 (SSVC 2.0.3).

timeline

  1. 15 Apr 2020Published
  2. 10 May 2020First public exploit or proof of concept · 24 days later
  3. 7 Jan 2025Added to CISA KEV (exploited in the wild) · 1,703 days (about 5 years) later
  4. 11 Jan 2025CISA SSVC assessment: exploitation active · 4 days later
  5. 28 Jan 2025CISA remediation due date (US federal agencies) · 17 days later
  6. 12 Jan 2026CVE record last updated · 350 days (about 12 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 294 days (about 10 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
5 references in the CVE record: 5 links

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved