LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3026: Vulnerability in the Oracle Banking Payments component of Oracle Financial Services Applications (subcompon...

Vulnerability in the Oracle Banking Payments component of Oracle Financial Services Applications (subcomponent: Payments Core). Supported versions that are affected are 12.2.0, 12.3.0, 12.4.0, 12.5.0 and 14.1.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Banking Payments. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Banking Payments, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Banking Payments accessible data as well as unauthorized read access to a subset of Oracle Banking Payments accessible data. CVSS 3.0 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2018-3026 affects Oracle Banking Payments and can let a low-privileged user with HTTP access alter or read some payment-system data if another person interacts with the attack. It is not listed as KEV, so the provided sources do not support active exploitation claims. Exposure is most likely where affected Oracle Banking Payments versions are reachable over HTTP by low-privileged authenticated users. Business impact depends on what payment data the application can access and whether user interaction can be induced. Prioritize remediation for banking environments where Oracle Banking Payments is internet-facing or broadly reachable by internal users. Treat this as a data integrity and confidentiality issue, not an availability crisis, unless local exposure is high. Mitigation focus: Identify Oracle Banking Payments deployments and versions 12.2.0, 12.3.0, 12.4.0, 12.5.0, and 14.1.0.; Review Oracle's July 2018 CPU advisory and apply vendor-provided fixes for the affected product/version.; Restrict HTTP access to trusted networks and authenticated business users where operationally possible..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2018-3026 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationBanking Payments12.2.0, 12.3.0, 12.4.0, 12.5.0, 14.1.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.