Threats / Oracle / CVE-2017-3506
CVE-2017-3506
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
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-034EPSS 0.96281 (verify live)5Exploit Weaponized · public PoC6CVSS 7.4 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
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
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).
Probability (EPSS)
EPSS 0.96281 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) · Affected: Oracle, WebLogic Server. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · 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 2597 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 public proof-of-concept / detection template). Catalog entries: 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 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