basicsecurity.net
Proof, not just disclosure.
Threats / Oracle / CVE-2020-14750
CVE-2020-14750 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Oracle WebLogic Server vulnerability

Oracle WebLogic Server contains an unspecified vulnerability allowing unauthenticated remote code execution. The vulnerability is actively exploited in the wild.

Verdict

Today item — known-exploited.

An unauthenticated attacker can execute arbitrary code on vulnerable WebLogic Server instances without authentication. Active exploitation in the wild and high EPSS score indicate immediate risk to exposed deployments.

CISA KEV Yes · 2021-11-033EPSS 0.9927 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
11 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 2021-11-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.9927 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Oracle, WebLogic Server. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I identify a publicly exposed Oracle WebLogic Server instance on the network.
Business
Exposed WebLogic deployments become reconnaissance targets for threat actors.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I send a crafted request to the vulnerable endpoint without providing credentials.
Business
Authentication bypass eliminates a primary security control, lowering attacker effort.
3

Lateral reach — past segmentation narrative 3

Attacker
I achieve remote code execution on the server through the unspecified vulnerability.
Business
Arbitrary code execution grants attackers full system compromise and lateral movement capability.
4

Data at risk — exfiltration narrative 4

Attacker
I establish persistence and exfiltrate sensitive data or deploy additional malware.
Business
Data breach, system compromise, and operational disruption result from initial RCE.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 11 reported-exploitation source(s)
  • Public exploit availability
  • Catalogued by oracle (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by oracleCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.