Threats / Oracle / CVE-2020-2883
CVE-2020-2883
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Oracle WebLogic Server vulnerability
Oracle WebLogic Server contains an unspecified vulnerability exploitable by unauthenticated attackers over IIOP or T3 protocols. The vulnerability is actively exploited in the wild with high EPSS score.
Verdict
Today item — known-exploited.
Unauthenticated remote attackers can exploit this vulnerability without credentials via network protocols IIOP or T3 to compromise WebLogic Server instances. Active exploitation in the wild indicates immediate risk to exposed deployments.
CISA KEV Yes · 2025-01-075EPSS 0.94928 (verify live)6Exploit Weaponized · public PoC7CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-01-07).
Probability (EPSS)
EPSS 0.94928 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Oracle, WebLogic Server. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.0, set at disclosure.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1728 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify a WebLogic Server instance exposed on the network and accessible via IIOP or T3 protocols without authentication requirements.
Business
Exposed WebLogic infrastructure becomes a direct target for opportunistic attackers scanning for vulnerable instances.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I send a crafted request through the unprotected IIOP or T3 channel to trigger the unspecified vulnerability in the server process.
Business
The vulnerability allows unauthorized code execution or information disclosure within the application server environment.
3
Lateral reach — past segmentation narrative 3
Attacker
I gain execution context within the WebLogic Server process to deploy malicious code or extract sensitive data.
Business
Compromised WebLogic instances can be used to access backend systems, databases, and intellectual property hosted within the enterprise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05