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

Oracle WebLogic Server vulnerability

Oracle WebLogic Server contains an OS command injection vulnerability allowing arbitrary code execution through specially crafted HTTP requests with malicious XML documents.

Verdict

Today item — known-exploited.

This OS command injection vulnerability in WebLogic Server enables unauthenticated remote code execution. The high EPSS score and active exploitation in the wild indicate significant risk to exposed instances.

CISA KEV Yes · 2024-06-033EPSS 0.96015 (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 2024-06-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.96015 — 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
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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 craft an HTTP request containing a malicious XML document targeting the WebLogic Server endpoint.
Business
Exposed WebLogic instances become entry points for unauthorized access and system compromise.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I inject OS commands through the XML parsing mechanism to execute arbitrary code on the server.
Business
Attackers gain command execution privileges equivalent to the WebLogic process user account.
3

Lateral reach — past segmentation narrative 3

Attacker
I establish persistence and move laterally within the network from the compromised server.
Business
Internal systems and data repositories become vulnerable to further exploitation and data exfiltration.
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)
  • CWE weakness mapping (NVD)
  • 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.