cve.bz

CVE-2026-0495 sap se sap fiori app (intercompany balance reconciliation)

5.1 mediumEPSS 0.2%

Medium (5.1) in sap se sap fiori app (intercompany balance reconciliation). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
SAP Fiori App Intercompany Balance Reconciliation allows an attacker with high privileges to send uploaded files to arbitrary emails which could enable effective phishing campaigns. This has low impact on confidentiality, integrity and availability of the application.

Severity

CVSS 3.1

5.1 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-01-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-15 External Control of System or Configuration Setting
OWASP Top 10
A02:2025 Security Misconfiguration
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-0495 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-0495?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-0495?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-0495 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)UIAPFI70 500
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)600
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)700
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)800
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)900
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)901
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)902
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)S4CORE 102
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)103
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)104
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)105
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)106
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)107
SAP_SE SAP Fiori App (Intercompany Balance Reconciliation)108

Attack patterns (CAPEC)

  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-69 Target Programs with Elevated Privileges Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-146 XML Schema Poisoning Likelihood: Low · Severity: High
  • CAPEC-176 Configuration/Environment Manipulation Severity: Medium
  • CAPEC-203 Manipulate Registry Information Severity: Medium
  • CAPEC-270 Modification of Registry Run Keys Likelihood: Medium · Severity: Medium
  • CAPEC-271 Schema Poisoning Likelihood: Low · Severity: High
  • CAPEC-579 Replace Winlogon Helper DLL

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON