Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with valid low-privilege account
-
DeliveryUpload file of dangerous type
-
ExploitBypass upload type restrictions
-
ExecutionInduce user interaction to trigger file
-
ImpactExecute attacker code in app context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated session to IBM Cyber Fraud (PR:L - the attacker must already possess valid low-privilege application credentials) and additional user interaction (UI:R), meaning a victim must process, open, or otherwise interact with the maliciously uploaded file for code execution to occur. The concrete prerequisite is access to the product's file-upload functionality, which fails to restrict dangerous file types (CWE-434). Limiting factors that reduce realistic risk: the mandatory authentication requirement blocks anonymous internet attackers, the required user interaction prevents fully automated exploitation, and the vulnerability is confined to the narrow installed base running Cyber Fraud versions 1.0.0 through 1.0.2. |
| Impact | This is a moderate, context-dependent risk rather than a top-priority emergency. The vendor CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N, 6.8) indicates network reach and low complexity but requires an authenticated attacker (PR:L) AND user interaction (UI:R), both of which meaningfully constrain real-world exploitation. There is NO CISA KEV listing, NO EPSS score provided in the input, and NO public exploit identified, so there is no evidence of active or widespread exploitation - the risk here is theoretical/potential, not demonstrated. A notable internal conflict exists: the CWE-434 unrestricted-file-upload class and the 'RCE' tag imply arbitrary code execution, yet the vendor-scored vector shows C:H but I:N and A:N, which is inconsistent with genuine code execution (which normally yields integrity and availability impact as well); this suggests either a conservative/atypical vendor scoring or that the practical impact is primarily disclosure - verify impact scope with IBM advisory node 7290671. Bottom line: prioritize patching for environments actually running IBM Cyber Fraud, but this is not a drop-everything internet-wide threat given the authentication and user-interaction prerequisites and the absence of exploitation signals. |
| Exploit ScenarioDerived | An attacker who already holds valid (low-privilege) credentials to IBM Cyber Fraud uploads a file of a dangerous type that bypasses upload restrictions; once the file is processed or a user is induced to interact with it (UI:R), attacker-controlled code executes in the application context. No public exploit code has been identified at the time of analysis, so this scenario is inferred from the CWE-434 weakness and CVSS vector rather than a demonstrated PoC. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Arbitrary code execution in IBM Cyber Fraud 1.0.0 through 1.0.2 requires an authenticated low-privilege user to upload a file with a dangerous type and then depends on a victim interacting with that file; the upload handler does not restrict dangerous file types (CWE-434). The vendor CVSS score is 6.8, while the independent assessment rates confidentiality, integrity, and availability impact as high with scope unchanged; the mandatory authentication (PR:L) and user interaction (UI:R) limit anonymous, fully automated exploitation. No public exploit code or CISA KEV entry was identified at time of analysis, and the realistic risk is moderate and context-dependent rather than an emergency.
RemediationAI
No exact fixed version is identified in the provided intelligence; consult the IBM advisory at https://www.ibm.com/support/pages/node/7290671 for vendor-released updates and apply the earliest fixed release for Cyber Fraud 1.0.x. Until a patch is confirmed, restrict access to the file-upload functionality to trusted, least-privileged users and monitor upload activity, because exploitation requires an authenticated session. Enforce a server-side allowlist of permitted file extensions and MIME types, store uploaded files outside the web root, and disable script execution in upload directories; these controls may break legitimate uploads of unusual file types and require application changes. Add malware scanning and user awareness training so recipients do not open unexpected uploaded files, since the assessed vector requires user interaction (UI:R). No public exploit code or CISA KEV entry was identified at time of analysis, so these measures can be prioritized against the moderate, context-dependent risk.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
IBM Cyber Fraud is an enterprise fraud-management application. The issue is in its file-upload functionality, which accepts files without enforcing an allowlist of safe extensions or MIME types. CWE-434 (Unrestricted Upload of File with Dangerous Type) means an authenticated user can place executable or script-bearing content into the application. In the assessed scenario, code execution is not automatic: the vector includes UI:R, so a victim must open, process, or otherwise interact with the uploaded file for the payload to run. The vendor vector (AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N) emphasizes confidentiality impact with scope change, whereas the independent assessment (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H) treats impact as high across confidentiality, integrity, and availability without scope change. CPE strings were not included in the supplied intelligence, so exact platform bindings cannot be confirmed from the data.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N
Authenticated upload yields PR:L and vendor-noted UI:R; a genuine CWE-434 code-execution flaw should carry full C:H/I:H/A:H rather than the vendor's I:N/A:N.
Primary rating from Vendor (us).
CVSS VectorVendor: us
DescriptionCVE.org
IBM Cyber Fraud 1.0.0 through 1.0.2 could allow a remote authenticated attacker to execute arbitrary code due to unrestricted upload of a file with a dangerous type.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-106862
GHSA-64f8-2p9v-73qq
NVD
CVE.org
EPSS
Exploit-DB