How severe is CVE-2018-3027?

CVE-2018-3027 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2018-3027 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2018-3027?

CVE-2018-3027 primarily affects Oracle Banking Payments. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2018-3027?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2018-3027 published?

CVE-2018-3027 was published on 2018-07-18 and last updated on 2026-06-17.

CVE-2018-3027

CVE-2018-3027 is a high-severity vulnerability in Oracle Banking Payments with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 8.1)
CVSS v2: 5.5
EPSS exploit prediction: 2% (79th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Banking Payments
Published: 2018-07-18
Last modified: 2026-06-17

Description

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 of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Banking Payments accessible data as well as unauthorized access to critical data or complete access to all Oracle Banking Payments accessible data. CVSS 3.0 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Frequently asked questions

What is CVE-2018-3027?: 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 of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Banking Payments accessible data as well as unauthorized access to critical data or complete access to all Oracle Banking Payments accessible data. CVSS 3.0 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).
How severe is CVE-2018-3027?: CVE-2018-3027 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2018-3027 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-3027?: CVE-2018-3027 primarily affects Oracle Banking Payments. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2018-3027?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-3027 published?: CVE-2018-3027 was published on 2018-07-18 and last updated on 2026-06-17.

References

Affected products (5)

cpe:2.3:a:oracle:banking_payments:12.2.0:*:*:*:*:*:*:*
cpe:2.3:a:oracle:banking_payments:12.3.0:*:*:*:*:*:*:*
cpe:2.3:a:oracle:banking_payments:12.4.0:*:*:*:*:*:*:*
cpe:2.3:a:oracle:banking_payments:12.5.0:*:*:*:*:*:*:*
cpe:2.3:a:oracle:banking_payments:14.1.0:*:*:*:*:*:*:*

More vulnerabilities in Oracle Banking Payments

CVE-2019-13990 — Critical (CVSS 9.8): initDocumentParser in xml/XMLSchedulingDataProcessor.java in Terracotta Quartz Scheduler through 2.3.0 allows XXE…
CVE-2018-2705 — High (CVSS 8.8): Vulnerability in the Oracle Banking Payments component of Oracle Financial Services Applications (subcomponent:…
CVE-2018-2704 — High (CVSS 8.1): Vulnerability in the Oracle Banking Payments component of Oracle Financial Services Applications (subcomponent:…
CVE-2021-36090 — High (CVSS 7.5): When reading a specially crafted ZIP archive, Compress can be made to allocate large amounts of memory that finally…
CVE-2021-35517 — High (CVSS 7.5): When reading a specially crafted TAR archive, Compress can be made to allocate large amounts of memory that finally…
CVE-2021-35515 — High (CVSS 7.5): When reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result…

All CVEs affecting Oracle Banking Payments →