dbcve.org
3dexperience EnoviaApplication · 3ds

CVE-2025-0829

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 Markup 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 in the 3D Markup feature of ENOVIA Collaborative Industry Innovator allows attackers to inject malicious JavaScript code that executes when other users view crafted 3D markup content. This affects releases from R2022x through R2024x.

MitigationApply vendor-provided patches for CVE-2025-0829 and implement additional input validation and output encoding for the 3D Markup functionality.

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. Verify ENOVIA installation
    Confirm 3ds 3dexperience Enovia Collaborative Industry Innovator is deployed in your environment. Check application server or software inventory for ENOVIA components.
    Affected if ENOVIA is not installed, the CVE does not apply.
  2. Check installed ENOVIA version
    Locate the ENOVIA version information in your installation (typically found in application metadata, about page, or version configuration files). Compare against affected range: R2022x through R2024x.
    Affected if Installed version falls within R2022x through R2024x, the environment is in the affected range.
  3. Confirm 3D Markup feature is enabled
    Determine whether the 3D Markup functionality is active and accessible to users in your ENOVIA deployment. Check feature configuration or user access settings.
    Affected if 3D Markup feature is disabled or not accessible to users, the XSS payload cannot be triggered.
  4. Inspect stored 3D Markup content
    Review 3D Markup database tables or storage where markup data is persisted. Look for any markup entries containing unsanitized script tags, javascript: URIs, or event handler attributes.
    Affected if Malicious JavaScript code exists in stored 3D Markup content, the vulnerability is present and exploitable.

Your environment is affected if ENOVIA Collaborative Industry Innovator versions R2022x through R2024x are running with the 3D Markup feature enabled and users can create or view 3D markup content.

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

Apply vendor-provided patches for CVE-2025-0829 and implement additional input validation and output encoding for the 3D Markup functionality.

Recommended fix Moderate confidence

3DExperience R2024x with security patch for CVE-2025-0829 (contact vendor for exact patch level)

  1. 1. Identify the current 3DExperience Enovia version in use by checking the ENOVIA Collaborative Industry Innovator installation
  2. 2. Contact Dassault Systèmes technical support or visit the 3DSS customer portal to obtain the security update for CVE-2025-0829
  3. 3. Request and apply the R2024x security patch that addresses the stored XSS vulnerability in 3D Markup
  4. 4. After applying the patch, verify the 3D Markup functionality works correctly
  5. 5. Test that the XSS vulnerability is no longer exploitable by attempting to insert script content in 3D Markup annotations
Caveat Contact vendor for specific patch release notes and any compatibility considerations

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

Fix this in 3dexperience Enovia Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0829 — 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-0829 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