How severe is CVE-2016-5623?

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

Is CVE-2016-5623 being actively exploited?

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

What products are affected by CVE-2016-5623?

CVE-2016-5623 primarily affects Oracle Flexcube Private Banking. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2016-5623?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2016-5623 published?

CVE-2016-5623 was published on 2017-01-27 and last updated on 2026-06-17.

CVE-2016-5623

CVE-2016-5623 is a medium-severity vulnerability in Oracle Flexcube Private Banking with a CVSS 3.x base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-254.

Key facts

Severity: Medium (CVSS 3.x base score 5.4)
CVSS v2: 5.5
EPSS exploit prediction: 1% (60th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-254
Affected product: Oracle Flexcube Private Banking
Published: 2017-01-27
Last modified: 2026-06-17

Description

Vulnerability in the Oracle FLEXCUBE Private Banking component of Oracle Financial Services Applications (subcomponent: Product / Instrument Search). Supported versions that are affected are 2.0.1, 2.2.0 and 12.0.1. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle FLEXCUBE Private Banking. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle FLEXCUBE Private Banking accessible data as well as unauthorized read access to a subset of Oracle FLEXCUBE Private Banking accessible data. CVSS v3.0 Base Score 5.4 (Confidentiality and Integrity impacts).

Frequently asked questions

What is CVE-2016-5623?: Vulnerability in the Oracle FLEXCUBE Private Banking component of Oracle Financial Services Applications (subcomponent: Product / Instrument Search). Supported versions that are affected are 2.0.1, 2.2.0 and 12.0.1. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle FLEXCUBE Private Banking. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle FLEXCUBE Private Banking accessible data as well as unauthorized read access to a subset of Oracle FLEXCUBE Private Banking accessible data. CVSS v3.0 Base Score 5.4 (Confidentiality and Integrity impacts).
How severe is CVE-2016-5623?: CVE-2016-5623 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2016-5623 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (60th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-5623?: CVE-2016-5623 primarily affects Oracle Flexcube Private Banking. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-5623?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2016-5623 published?: CVE-2016-5623 was published on 2017-01-27 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:a:oracle:flexcube_private_banking:2.0.1:*:*:*:*:*:*:*
cpe:2.3:a:oracle:flexcube_private_banking:2.2.0:*:*:*:*:*:*:*
cpe:2.3:a:oracle:flexcube_private_banking:12.0.1:*:*:*:*:*:*:*

More vulnerabilities in Oracle Flexcube Private Banking

CVE-2013-4316 — Critical (CVSS 10.0): Apache Struts 2.0.0 through 2.3.15.1 enables Dynamic Method Invocation by default, which has unknown impact and attack…
CVE-2020-11998 — Critical (CVSS 9.8): A regression has been introduced in the commit preventing JMX re-bind. By passing an empty environment map to…
CVE-2020-5413 — Critical (CVSS 9.8): Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When…
CVE-2020-11973 — Critical (CVSS 9.8): Apache Camel Netty enables Java deserialization by default. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to…
CVE-2020-11972 — Critical (CVSS 9.8): Apache Camel RabbitMQ enables Java deserialization by default. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to…
CVE-2019-12419 — Critical (CVSS 9.8): Apache CXF before 3.3.4 and 3.2.11 provides all of the components that are required to build a fully fledged OpenId…

All CVEs affecting Oracle Flexcube Private Banking →

Other CWE-254 vulnerabilities

CVE-2016-5788 — Critical (CVSS 10.0): General Electric (GE) Bently Nevada 3500/22M USB with firmware before 5.0 and Bently Nevada 3500/22M Serial have open…
CVE-2015-3972 — Critical (CVSS 10.0): The web interface on Janitza UMG 508, 509, 511, 604, and 605 devices supports only short PIN values for authentication,…
CVE-2015-1158 — Critical (CVSS 10.0): The add_job function in scheduler/ipp.c in cupsd in CUPS before 2.0.3 performs incorrect free operations for…
CVE-2019-15149 — Critical (CVSS 9.8): core.py in Mitogen before 0.2.8 has a typo that drops the unidirectional-routing protection mechanism in the case of a…
CVE-2017-8227 — Critical (CVSS 9.8): Amcrest IPM-721S V2.420.AC00.16.R.20160909 devices have a timeout policy to wait for 5 minutes in case 30 incorrect…
CVE-2016-9568 — Critical (CVSS 9.8): A security design issue can allow an unprivileged user to interact with the Carbon Black Sensor and perform…

Browse all CWE-254 vulnerabilities →