CVE-2025-0598
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 · uneditedA stored Cross-site Scripting (XSS) vulnerability affecting Relations in ENOVIA Collaborative Industry Innovator from Release 3DEXPERIENCE R2023x 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 confidenceStored Cross-site Scripting (XSS) vulnerability in the Relations feature of ENOVIA Collaborative Industry Innovator allows attackers to inject malicious JavaScript that persists in the database and executes in victim users' browser sessions when the tainted data is displayed.
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= r2023x= r2024xCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify ENOVIA installationLocate the 3ds 3dexperience Enovia installation directory or check the application's login/version page for product identificationAffected if The product is 3ds 3dexperience Enovia Collaborative Industry Innovator
-
Determine installed versionAccess the ENOVIA administration console or version information page, or run the version check command specific to the 3dexperience platformAffected if The installed version is r2023x or r2024x (any minor version within these major releases)
-
Verify Relations feature is accessibleLog into ENOVIA and navigate to the Relations feature module within the Collaborative Industry Innovator applicationAffected if The Relations feature is available and user has access to create or view relation records
-
Inspect Relations data for injected scriptsQuery the Relations data objects or view existing Relations records in the UI, looking for script tags, javascript: URIs, or event handler attributes in name/description fieldsAffected if Any Relations records contain unsanitized HTML or script content that would execute when viewed
-
Review database for XSS payloadsQuery the underlying database tables storing Relations data (specific table names depend on ENOVIA schema) for patterns like <script, javascript:, onload=, onerror= in text fieldsAffected if The database contains persisted XSS payloads in Relations-related tables
A user is affected if they run ENOVIA r2023x or r2024x with the Relations feature enabled and have stored malicious script content in Relations records that executes when other users view that data.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement strict input validation and context-aware output encoding for all user-supplied data in the Relations feature; apply vendor patch when released.
3DEXPERIENCE R2025x or later release
- Check the current ENOVIA Collaborative Industry Innovator version by accessing the 3DEXPERIENCE platform administration console
- Contact Dassault Systèmes customer support or visit the official 3DS support portal (support.3ds.com) to obtain the latest fixed version
- Plan upgrade during a maintenance window to minimize business impact
- Before upgrading, review release notes for R2025x or later versions for XSS-related security fixes
- Perform a backup of the ENOVIA database and configuration files
- Execute the upgrade following the official 3DEXPERIENCE upgrade documentation
- After upgrade, verify that the Relations functionality works correctly
- Test that the XSS vulnerability is remediated by attempting to inject script content in Relations fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0598 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0598 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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