CVE-2018-2419 [Low] | Security Vulnerability in Sapscore

SAP Enterprise Financial Services (SAPSCORE 1.11, 1.12; S4CORE 1.01, 1.02; EA-FINSERV 6.04, 6.05, 6.06, 6.16, 6.17, 6.18, 8.0) does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.19%	0.86%	+0.67%
2	2025-03-30	0.15%	0.19%	+0.04%
3	2025-03-29	—	0.15%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.19%

0.86%

+0.67%

2025-03-30

0.15%

0.19%

+0.04%

2025-03-29

—

0.15%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
3.7	3.0	LOW	`CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	1.2	2.5	[email protected]
4.6	3.0	MEDIUM	`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.1	2.5	[email protected]
5.5	2.0	MEDIUM	`AV:N/AC:L/Au:S/C:P/I:P/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:S) A single authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:N) No availability impact.	8.0	4.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

3.7

3.0

LOW

CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

1.2

2.5

[email protected]

4.6

3.0

MEDIUM

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.1

2.5

[email protected]

5.5

2.0

MEDIUM

AV:N/AC:L/Au:S/C:P/I:P/A:N Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:S): A single authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:N): No availability impact.

8.0

4.9

[email protected]

Affected software / configurations for CVE-2018-2419

Vendor	Product	Version	Raw CPE
sap	sapscore	1.11	cpe:2.3:a:sap:sapscore:1.11:::::::*
sap	sapscore	1.12	cpe:2.3:a:sap:sapscore:1.12:::::::*
sap	s4core	1.01	cpe:2.3:a:sap:s4core:1.01:::::::*
sap	s4core	1.02	cpe:2.3:a:sap:s4core:1.02:::::::*
sap	ea-finserv	6.04	cpe:2.3:a:sap:ea-finserv:6.04:::::::*
sap	ea-finserv	6.05	cpe:2.3:a:sap:ea-finserv:6.05:::::::*
sap	ea-finserv	6.06	cpe:2.3:a:sap:ea-finserv:6.06:::::::*
sap	ea-finserv	6.16	cpe:2.3:a:sap:ea-finserv:6.16:::::::*
sap	ea-finserv	6.17	cpe:2.3:a:sap:ea-finserv:6.17:::::::*
sap	ea-finserv	6.18	cpe:2.3:a:sap:ea-finserv:6.18:::::::*
sap	ea-finserv	8.0	cpe:2.3:a:sap:ea-finserv:8.0:::::::*

References for CVE-2018-2419

URL	Tags
http://www.securityfocus.com/bid/104116	Third Party Advisory VDB Entry
https://blogs.sap.com/2018/05/08/sap-security-patch-day-may-2018/	Vendor Advisory
https://launchpad.support.sap.com/#/notes/2596627	Permissions Required

URL

CVE-2018-2419

Exploit prediction scoring system (EPSS) score for CVE-2018-2419

Common vulnerability scoring system (CVSS) metrics for CVE-2018-2419

Weakness enumeration for CVE-2018-2419

Affected software / configurations for CVE-2018-2419

References for CVE-2018-2419