CVE-2025-0599
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 Document Management in ENOVIA Collaborative Industry Innovator on 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 confidenceA stored Cross-site Scripting (XSS) vulnerability exists in the Document Management component of ENOVIA Collaborative Industry Innovator on the 3DEXPERIENCE R2024x platform. An attacker with document upload/management access can embed malicious JavaScript code into document metadata or content, which will execute in the browsers of other users who subsequently view or interact with the affected documents.
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= 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 installed ENOVIA versionAccess the ENOVIA administration console or check the platform version information typically found in the About section or system information page. Look for version string 'r2024x' specifically.Affected if The installed version is exactly r2024x (the affected version)
-
Confirm Document Management module is activeLog into the 3DEXPERIENCE platform and navigate to the Document Management component. Check if the module is accessible and functional for your user account.Affected if Document Management module is enabled and accessible to users with document upload permissions
-
Review document metadata for injected scriptsUsing the Document Management interface, inspect document properties, titles, descriptions, and custom metadata fields. Look for any unexpected script tags, javascript: URLs, or event handler attributes (onclick, onerror, etc.) in these fields.Affected if Documents contain unsanitized script content in metadata fields that would execute when viewed
-
Audit document content for malicious payloadsOpen or preview existing documents through the Document Management viewer. Check document content areas where user-supplied data is displayed, including embedded links, annotations, and comments.Affected if Stored XSS payloads exist in document content and execute when other users view the documents
You are affected if running ENOVIA 3DEXPERIENCE platform version r2024x with the Document Management module enabled and users have uploaded documents containing unsanitized JavaScript in metadata or content fields.
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.
From vendor dataImplement robust input validation and context-aware output encoding for all user-supplied data within the Document Management module. Apply Content Security Policy (CSP) headers to mitigate XSS execution, and sanitize document metadata and content before storage and upon display.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0599 — 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-0599 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