CVE-2026-0493VulnerabilityPublished 13 Jan 2026

CVE-2026-0493: SAP Fiori App (Intercompany Balance Reconciliation) · Cross-Site Request Forgery

Affects SAP Fiori App (Intercompany Balance Reconciliation)Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SAP_SESAP Fiori App (Intercompany Balance Reconciliation)	Affected =600 =700 =800 =900 =901 =902 =103 =104 =105 =106 =107 =108 =109	Fixed in–

AI-suggested

European organizations should implement the following specific mitigations: 1) Immediately review and apply any SAP patches or security notes related to CVE-2026-0493 once released. 2) Enforce strict CSRF token validation in SAP Fiori applications, ensuring that all state-changing requests require valid anti-CSRF tokens. 3) Restrict access to SAP Fiori apps through network segmentation and VPNs to limit exposure to trusted users only. 4) Implement least privilege principles, ensuring users have only the necessary permissions to perform their roles, reducing the impact of compromised accounts. 5) Monitor SAP application logs for unusual or unauthorized state-changing requests that could indicate exploitation attempts. 6) Educate users about the risks of CSRF and encourage safe browsing practices, especially when accessing SAP portals. 7) Utilize Web Application Firewalls (WAFs) with custom rules to detect and block suspicious CSRF attack patterns targeting SAP Fiori endpoints. 8) Conduct regular security assessments and penetration testing focused on SAP Fiori applications to identify and remediate CSRF and related vulnerabilities proactively.

Description

CVE-2026-0493 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability affecting the SAP Fiori App Intercompany Balance Reconciliation. It allows an attacker to perform state-changing actions on behalf of an authenticated user without their consent, potentially impacting the integrity of financial reconciliation data. The vulnerability does not affect confidentiality or availability and requires the attacker to have some level of privileges (PR:L) but no user interaction is needed. It affects multiple versions of SAP Fiori and S4CORE components widely used in enterprise environments. No known exploits are currently reported in the wild. European organizations using the affected SAP versions should prioritize patching and implement CSRF protections to mitigate risks. Countries with significant SAP enterprise deployments and financial sectors are more likely to be impacted. The CVSS score is 4.3, reflecting a medium risk primarily due to integrity impact and ease of exploitation without user interaction.

Impact

For European organizations, especially those in finance, manufacturing, and multinational corporations relying on SAP ERP systems, this vulnerability could lead to unauthorized modification of intercompany financial data, impacting data integrity and potentially causing accounting discrepancies or compliance issues. While confidentiality and availability remain unaffected, the integrity compromise could disrupt financial reconciliation processes, leading to erroneous financial statements or audit failures. The risk is heightened in environments where users have elevated privileges and where SAP Fiori apps are accessible over networks without additional protective controls. Given the widespread use of SAP in Europe, particularly in Germany, France, and the UK, the impact could affect critical business operations and regulatory compliance. Attackers exploiting this vulnerability could manipulate financial data silently, complicating detection and remediation efforts. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits after vulnerability disclosure. Organizations failing to address this issue may face increased risk of fraud, financial misstatements, and reputational damage.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 03:03 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats