CriticalCVE-2025-6204

    Dassault Systèmes DELMIA Apriso Code Injection Vulnerability (CVE-2025-6204)

    Published In CISA KEV since Sources: pwn.watch, CVE.org

    Share

    What is affected, what to do

    An Improper Control of Generation of Code (Code Injection) vulnerability affecting DELMIA Apriso from Release 2020 through Release 2025 could allow an attacker to execute arbitrary code.

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Dassault Systèmes DELMIA Apriso gte Release 2020 Golden..*
    • Dassault Systèmes DELMIA Apriso gte Release 2021 Golden..*
    • Dassault Systèmes DELMIA Apriso gte Release 2022 Golden..*
    • Dassault Systèmes DELMIA Apriso gte Release 2023 Golden..*
    • Dassault Systèmes DELMIA Apriso gte Release 2024 Golden..*
    • Dassault Systèmes DELMIA Apriso gte Release 2025 Golden..*

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.0

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    8.0

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: pwn.watch, CVE.org

    79.6 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.60

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    229.49 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.0 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    79.6 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.60
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 28 October 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-94

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw gives an attacker arbitrary code execution on a central manufacturing execution system. It needs high privileges and has elevated attack complexity, but it crosses the application boundary (scope change) and fully compromises confidentiality, integrity and availability. Exploitation likelihood is rated very high, and CISA does not flag known ransomware use. Attackers typically pair this kind of bug with stolen or weak admin credentials or authorisation weaknesses to gain a foothold on the MES server and pivot towards OT-adjacent networks. For manufacturers and KRITIS operators running Apriso in production, treat this as critical. Reachability from IT or internet networks and shared admin accounts raise the urgency further, while fully isolated instances behind MFA-protected access can be patched in the next maintenance window.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory: Identify every DELMIA Apriso instance on Releases 2020 through 2025 (Golden), including test, training and plant-level servers. Cover application and web servers as well as their database servers.
      • Patch: Apply the Dassault Systèmes fix for CVE-2025-6204 (patch available from the vendor — look up the exact version in the vendor advisory or the 3DS support portal). Patch internet- or IT-reachable instances first, then production MES in the next coordinated maintenance window.
      • Restrict exposure: Block Apriso web interfaces and services from the internet and from guest and office networks now. Allow access only via jump host or VPN from defined admin and plant subnets.
      • Review privileged accounts: Exploitation requires high privileges. Audit all Apriso administrator and developer accounts (e.g. Process Builder and configuration rights) plus the Apriso service accounts and backend SQL logins. Disable unused accounts and rotate passwords and secrets, especially shared or long-unchanged credentials.
      • Preserve evidence before patching: Capture a snapshot or image, IIS logs, Windows event logs and an export of recently modified process definitions first, so the update does not silently overwrite webshells or tampering.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation (IEC 62443 zones/conduits): Place Apriso in a dedicated Level 3 MES zone between IT and OT. Default-deny internet egress from Apriso servers, except defined update targets. Only allow connections to SCADA and PLC layers through explicitly approved conduits.
      • Reverse proxy/WAF: Expose Apriso admin and designer paths only to admin subnets. Block or alert on POST bodies containing code fragments such as System.Diagnostics.Process, Process.Start, powershell, cmd.exe /c or large Base64 blobs in form fields.
      • IAM/least privilege: Separate admin and development rights from operator roles. Enforce MFA on the upstream access path (VPN/jump host). Run the Apriso service and IIS app pool identity without local admin rights and with no domain-admin linkage.
      • Endpoint hardening: Use WDAC or AppLocker on Apriso servers to restrict cmd.exe, powershell.exe, certutil.exe, bitsadmin.exe and mshta.exe under the app pool identity. Set the EDR "web server spawns shell" rule to block.
      • Integrity controls: Remove write access to Apriso web and binary directories from the app pool identity. Enable file integrity monitoring on .aspx, .ashx, .asmx, .config and .dll files.

    3. Runbook step 3

      Detection rules

      • Sysmon EID 1 / EDR process ancestry: Shell or recon tooling spawned by the IIS worker. KQL: DeviceProcessEvents | where InitiatingProcessFileName =~ "w3wp.exe" and FileName in~ ("cmd.exe","powershell.exe","pwsh.exe","whoami.exe","net.exe","nltest.exe","certutil.exe","rundll32.exe"). Note that csc.exe may be legitimate during dynamic .NET compilation, so baseline it and alert on deviations.
      • Sysmon EID 11 / FIM: New or modified script or DLL files in Apriso web and install directories outside maintenance windows. Sigma shape: TargetFilename|contains: '\Apriso\' with TargetFilename|endswith: ['.aspx','.ashx','.dll','.config'].
      • IIS access logs: POSTs to admin, designer or configuration endpoints from source IPs outside admin subnets. Also watch for unusually large request bodies and HTTP 200 responses on previously unseen .aspx paths. SPL: index=iis host=apriso* cs_method=POST NOT c_ip IN (10.x.admin/24) | stats count by c_ip, cs_uri_stem.
      • Windows Security log: Event 4624 (logon type 3/10) and 4672 for Apriso admin and service accounts from atypical sources. Event 4688 with the app pool identity as subject. Event 4720 or 4732 when new local accounts or group memberships appear on MES hosts.
      • Network telemetry (Zeek/Suricata): Outbound connections from Apriso servers to internet destinations, tunnelling services or newly registered domains via DNS. Also lateral SMB and WinRM traffic (445/5985/5986) from the MES zone into OT or domain controller segments.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    An Improper Control of Generation of Code (Code Injection) vulnerability affecting DELMIA Apriso from Release 2020 through Release 2025 could allow an attacker to execute arbitrary code.

    Source: pwn.watch, NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    Dassault SystèmesDELMIA Apriso
    • ≥ Release 2021 Golden
    • ≥ Release 2020 Golden
    • ≥ Release 2022 Golden
    • ≥ Release 2024 Golden
    • ≥ Release 2025 Golden
    • ≥ Release 2023 Golden
    • —
    • —
    • —
    • —
    • —
    • —
    3dsdelmia_apriso
    • 2020 – ≤ 2025
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-94Improper Control of Generation of Code ('Code Injection')

      Base

      The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

      Entry at MITRE CWE-94

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • 3ds.comDassault Systèmes advisory: Dassault Systèmes DELMIA AprisoVendor advisory, pwn-watch
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-6204government-resource, US government resource
    • pwn.watchpwn.watch: Dassault Systèmes DELMIA Apriso: 2 exploited vulnerabilities (CVE-2025-6204, CVE-2025-6205)pwn-watch
    • 3ds.comDassault Systèmes advisory: Dassault Systèmes DELMIA Aprisopwn-watch
    • NVD (NIST)NVD: CVE-2025-6204pwn-watch
    • NVD (NIST)NVD: CVE-2025-6205pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-6204
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-6204"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-6204.svg?lang=en" alt="CVE-2025-6204 – NEOSEC Intel" height="20"></a>