CVE-2025-10559VulnerabilityPublished 31 Mar 2026

CVE-2025-10559: Dassault Systèmes DELMIA Factory Resource Manager · Path Traversal

Affects Dassault Systèmes DELMIA Factory Resource ManagerSource CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.1High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% 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:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 31 Mar 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 2026-10-25.

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
Dassault SystèmesDELMIA Factory Resource Manager	Affected ≥ Release 3DEXPERIENCE R2023x Golden, ≤ Release 3DEXPERIENCE R2023x.FP.CFA.2541 ≥ Release 3DEXPERIENCE R2024x Golden, ≤ Release 3DEXPERIENCE R2024x.FP.CFA.2537 ≥ Release 3DEXPERIENCE R2025x Golden, ≤ Release 3DEXPERIENCE R2025x.FP.CFA.2514	Fixed in–

AI-suggested

To mitigate CVE-2025-10559, organizations should implement the following specific measures: 1) Monitor Dassault Systèmes advisories closely and apply patches or updates as soon as they become available for the affected DELMIA Factory Resource Manager releases. 2) Restrict network access to the Factory Resource Manager servers by implementing network segmentation and firewall rules to limit exposure to trusted users and systems only. 3) Enforce the principle of least privilege by ensuring that user accounts and service accounts interacting with the Factory Resource Manager have minimal necessary permissions, reducing the impact of compromised credentials. 4) Conduct input validation and sanitization on any user-supplied file path parameters at the application or proxy level if possible, to detect and block path traversal attempts. 5) Implement file integrity monitoring on critical directories to detect unauthorized file modifications or creations. 6) Review and harden server configurations to limit file system permissions, ensuring the application process cannot access directories beyond its scope. 7) Employ logging and alerting mechanisms to detect suspicious file access patterns indicative of path traversal exploitation attempts. 8) Conduct regular security assessments and penetration testing focused on path traversal and related vulnerabilities in the Factory Resource Manager environment.

Description

A Path Traversal vulnerability affecting Factory Resource Management in DELMIA Factory Resource Manager from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2025x allows an attacker to read or write files in specific directories on the server.

Impact

The primary impact of CVE-2025-10559 is the unauthorized disclosure of sensitive information due to the ability to read arbitrary files on the server. This can lead to exposure of intellectual property, configuration files, credentials, or other sensitive data critical to manufacturing operations. The ability to write files, although limited, could allow attackers to modify configuration or operational files, potentially leading to process disruptions or further compromise. Given the industrial context, such unauthorized access could disrupt factory resource planning, cause operational delays, or facilitate further attacks such as ransomware or espionage. Organizations worldwide that rely on DELMIA Factory Resource Manager for factory automation and resource management face risks to confidentiality and operational integrity. The vulnerability could also be leveraged as a foothold for lateral movement within corporate networks. The absence of known exploits currently provides a window for mitigation, but the high CVSS score indicates a serious threat if exploited.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

3ds.com/trust-center/security/security-advisories/cve-2025-10559 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Mar 2026, 19:19 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats