CVE-2026-24312 | Missing authorization check in SAP Business Workflow

An erroneous authorization check in SAP Business Workflow leads to privilege escalation. An authenticated administrative user can bypass role restrictions by leveraging permissions from a less sensitive function to execute unauthorized, high-privilege actions. This has a high impact on data integrity, with low impact on confidentiality and no impact on availability of the application.

Published: 2026-02-10 Last update: 2026-02-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-24312 is rated Low Risk (23.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.17%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-24312

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.02% 0.17% +0.15%
2 2026-02-10 0.02%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-24312

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.2 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
0.9 4.2 [email protected]
5.2 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
0.9 4.2 [email protected]

Weakness enumeration for CVE-2026-24312

Affected software / configurations for CVE-2026-24312

Vendor Product Version Raw CPE
sap sap_basis 752 cpe:2.3:a:sap:sap_basis:752:*:*:*:*:*:*:*
sap sap_basis 753 cpe:2.3:a:sap:sap_basis:753:*:*:*:*:*:*:*
sap sap_basis 754 cpe:2.3:a:sap:sap_basis:754:*:*:*:*:*:*:*
sap sap_basis 755 cpe:2.3:a:sap:sap_basis:755:*:*:*:*:*:*:*
sap sap_basis 756 cpe:2.3:a:sap:sap_basis:756:*:*:*:*:*:*:*
sap sap_basis 757 cpe:2.3:a:sap:sap_basis:757:*:*:*:*:*:*:*
sap sap_basis 758 cpe:2.3:a:sap:sap_basis:758:*:*:*:*:*:*:*
sap sap_basis 816 cpe:2.3:a:sap:sap_basis:816:*:*:*:*:*:*:*

References for CVE-2026-24312

URL Tags
https://me.sap.com/notes/3710111 Permissions Required
https://url.sap/sapsecuritypatchday Vendor Advisory
cvelogic Threat Intelligence