Security readout for executives and security teams
Plain-English summary
Oracle Commerce Guided Search / Experience Manager 11.4.0 contains a critical flaw that an unauthenticated network attacker can reach over HTTP. A successful attack could take over the affected application, exposing or altering commerce data and disrupting service. The supplied evidence does not establish whether exploitation is occurring in the wild.
Executive priority
Treat as an immediate remediation priority for confirmed 11.4.0 deployments, especially those reachable from the internet or partner networks. Potential impact is complete application takeover across confidentiality, integrity, and availability. Require rapid inventory, access restriction, vendor-guidance review, remediation validation, and evidence-based investigation without claiming an active incident solely from this disclosure.
Technical view
The Content Acquisition System component in version 11.4.0 is affected by improper authorization or missing authentication controls (CWE-284 and CWE-306). Exploitation requires network access over HTTP, with low complexity, no privileges, and no user interaction. Oracle assigns CVSS 3.1 score 9.8, reflecting high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure is limited by the supplied evidence to Oracle Commerce Guided Search / Oracle Commerce Experience Manager 11.4.0. Risk is greatest where the Content Acquisition System is reachable over HTTP from untrusted networks. The bundle does not identify affected configurations, ports, deployment patterns, or earlier versions.
Exploitation context
The vulnerability is described as easily exploitable and capable of application takeover without authentication. However, the supplied bundle marks it as absent from KEV and provides no cited evidence of active exploitation, public exploit availability, or observed attacks. Treat exploit status as unconfirmed, not as evidence that exploitation is impossible.
Researcher notes
The public bundle establishes affected version, component, attack vector, impact, CWEs, and CVSS characteristics, but not the vulnerable endpoint, root cause details, proof of concept, indicators, or exact remediation. Validation should remain non-destructive and focus on version, component presence, reachability, vendor remediation state, and relevant logging.
Mitigation direction
- Identify every deployment running the affected 11.4.0 release.
- Review Oracle's July 2026 advisory for the vendor-approved remediation.
- Restrict HTTP access to trusted networks while remediation is assessed and applied.
- Prioritize internet-facing or broadly reachable Content Acquisition System instances.
- Do not assume unsupported versions are safe; obtain vendor confirmation.
Validation and detection
- Confirm installed product and component versions using trusted asset records.
- Test whether affected HTTP interfaces are reachable from untrusted network segments.
- Verify vendor-recommended remediation is applied according to Oracle guidance.
- Review HTTP and application logs for anomalous unauthenticated activity.
- Document any exposure gaps because source-specific indicators were not provided.
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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCWE-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-61145 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.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.