Security readout for executives and security teams
Plain-English summary
A network attacker who can reach an affected Oracle WebLogic Server through T3 or IIOP may take control without credentials or user interaction. A successful compromise could expose data, alter systems, and disrupt services. The affected versions are explicitly identified, making rapid inventory and exposure review essential.
Executive priority
Treat as an immediate critical remediation program. Assign ownership, identify affected servers, reduce T3 and IIOP exposure, and follow Oracle guidance. Systems supporting sensitive data or essential services should receive first priority because successful exploitation may enable complete server takeover.
Technical view
CVE-2026-60672 is an unauthenticated Oracle WebLogic Server Core vulnerability affecting versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. It is reachable over T3 or IIOP and may result in server takeover. CVSS 3.1 is 9.8, with high confidentiality, integrity, and availability impact. CWE-306 indicates missing authentication for a critical function.
Likely exposure
Exposure exists where an affected WebLogic version accepts attacker-reachable T3 or IIOP connections. Internet-facing or broadly reachable management and application networks warrant the fastest review. The supplied sources do not identify default ports, configurations, or deployment patterns that guarantee vulnerability.
Exploitation context
The vulnerability requires network access but no authentication, privileges, or user interaction, and Oracle describes it as easily exploitable. The supplied bundle marks it absent from KEV and provides no evidence of active exploitation. That absence should not be interpreted as evidence that exploitation is not occurring.
Researcher notes
The public description establishes an unauthenticated, low-complexity network path through T3 or IIOP and complete impact across confidentiality, integrity, and availability. It does not disclose the vulnerable code path, prerequisites beyond network access, indicators of compromise, proof-of-concept availability, or confirmed exploitation. Avoid assuming that every WebLogic deployment exposes these protocols.
Mitigation direction
- Review Oracle's advisory and apply its supported remediation when available and applicable.
- Restrict T3 and IIOP access to explicitly authorized systems and trusted network paths.
- Prioritize affected internet-facing or broadly reachable WebLogic servers for immediate risk reduction.
- Use segmentation or temporary isolation where vendor remediation cannot be applied promptly.
Validation and detection
- Inventory WebLogic installations and confirm whether listed affected versions are present.
- Map which systems and external networks can reach T3 or IIOP services.
- Confirm Oracle advisory remediation has been applied according to vendor instructions.
- Reassess T3 and IIOP reachability after network restrictions or remediation.
- Review affected servers for unexplained access, configuration changes, or service disruption.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-60672 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9oracleVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Oracle AdvisoryCVE reference, oracle · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Functionality
Missing Authentication for Critical Functionality represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.