Summary
CVE-2026-12581 is a high-severity Session Fixation vulnerability (CWE-384) in Digiwin EasyFlow .NET, an enterprise web-based Business Process Management (BPM) and workflow platform widely deployed across Asia. An unauthenticated remote attacker can inject a known session identifier into a targeted user’s browser; once the victim authenticates, the attacker gains that user’s full application privileges — constituting a complete account takeover. The vulnerability carries a CVSS v4.0 score of 7.7 (High) and affects all versions up to and including 8.1.4.
Technical details
- Root cause: The application does not regenerate or invalidate the session token upon successful user authentication (CWE-384), allowing a session ID pre-planted by an attacker to remain valid after login.
- Trigger conditions: The attacker first delivers a known, attacker-controlled session ID to the victim’s browser (e.g., via a crafted link or injection mechanism); the vulnerability is triggered when the legitimate user subsequently logs in with that session active.
- Attack vector: Network-accessible (AV:N); no prior authentication required (PR:N); passive user interaction required — the victim must complete a normal login after the session has been fixed.
- Impact: Successful exploitation grants the attacker full control over the victim’s authenticated session, resulting in complete compromise of confidentiality, integrity, and availability within the EasyFlow .NET application (VC:H / VI:H / VA:H).
Affected software
- Digiwin EasyFlow .NET versions 8.1.4 and earlier
Severity
CVSS v3.1 base score: 7.5 (High)
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Upgrade Digiwin EasyFlow .NET to version 8.1.5 or later, which contains the vendor-provided fix as documented in the TWCERT/CC advisory published 2026-06-22.
- If immediate patching is not feasible: Restrict network-level access to EasyFlow .NET instances (e.g., via firewall rules or VPN enforcement) to limit the attacker’s ability to deliver a crafted session ID to targeted users from the open internet.
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

