dbcve.org
3dexperience EnoviaApplication · 3ds

CVE-2025-0826

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A stored Cross-site Scripting (XSS) vulnerability affecting 3D Navigate in ENOVIA Collaborative Industry Innovator from Release 3DEXPERIENCE R2022x through Release 3DEXPERIENCE R2024x allows an attacker to execute arbitrary script code in user's browser session.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stored Cross-site Scripting (XSS) vulnerability exists in the 3D Navigate component of ENOVIA Collaborative Industry Innovator from versions R2022x through R2024x. Attackers can inject malicious JavaScript code that persists in the application and executes in victim users' browser sessions when the stored payload is rendered.

MitigationImplement proper input validation and context-aware output encoding for all user-supplied data rendered by the 3D Navigate component. Apply Content Security Policy (CSP) headers as a defense-in-depth measure. Monitor for vendor patches for the R2022x-R2024x releases.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
3dexperience EnoviaApplication
Affected:>= r2022x, <= r2024x

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ENOVIA installation and version
    Locate the ENOVIA/3dexperience installation directory and check version files or About dialog. Common locations include the installation root or within the ENOVIA application directory. Look for version information displayed in the application or stored in configuration files.
    Affected if The installed version is R2022x, R2023x, or R2024x (inclusive of all point releases within these versions)
  2. Confirm 3D Navigate component is accessible
    Determine if the 3D Navigate component is enabled and accessible within the ENOVIA environment. This may be visible as a module, feature, or navigation option within the application's user interface or administration console.
    Affected if The 3D Navigate component is present and enabled in the application
  3. Review stored data in 3D Navigate for suspicious content
    Inspect the application's database or data storage where 3D Navigate component stores user-supplied content. Look for entries containing HTML, JavaScript, or script-related keywords in fields that could be rendered back to users.
    Affected if Malicious JavaScript code is found persisted in stored data within the 3D Navigate component
  4. Check application logs for XSS injection attempts
    Review ENOVIA server logs, access logs, or security audit logs for patterns indicative of XSS injection attempts targeting the 3D Navigate component. Look for script tags, javascript: protocols, or event handlers in request parameters.
    Affected if Logs show injection of script-related content into 3D Navigate fields or parameters

A user is affected if they have ENOVIA 3dexperience installed with a version between R2022x and R2024x inclusive AND the 3D Navigate component is enabled and accessible, with potentially malicious script content stored within it.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and context-aware output encoding for all user-supplied data rendered by the 3D Navigate component. Apply Content Security Policy (CSP) headers as a defense-in-depth measure. Monitor for vendor patches for the R2022x-R2024x releases.

Recommended fix Moderate confidence

3DEXPERIENCE R2025x or later release (beyond R2024x)

  1. Contact Dassault Systèmes customer support to obtain the latest 3DEXPERIENCE release that includes the security fix for CVE-2025-0826
  2. Request the R2025x or newer release that addresses the stored XSS vulnerability in 3D Navigate/ENOVIA Collaborative Industry Innovator
  3. Plan and schedule the upgrade in a non-production environment first
  4. Test critical ENOVIA workflows and 3D Navigate functionality after applying the upgrade
  5. Deploy the fixed release to production following standard change management procedures
Caveat Review Dassault Systèmes release notes for R2025x for any compatibility changes or deprecated features that may affect custom integrations or workflows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 3dexperience Enovia Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0826 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0826 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data