CVE-2025-10551
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 from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2025x 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 in ENOVIA Collaborative Industry Innovator's Document Management component allows attackers to inject malicious script code that persists in the system and executes in the browsers of users who access 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>= r2023x, <= r2025xCVSS 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.
-
Verify 3DEXPERIENCE platform installation and versionLocate the 3DEXPERIENCE installation directory or check system inventory for the exact version number (for example, using '3dxml' file properties, installation logs, or the platform's About dialog). Compare your installed version against the affected range: r2023x through r2025x.Affected if The installed version falls within r2023x to r2025x inclusive.
-
Confirm ENOVIA Collaborative Industry Innovator module is activeAccess the ENOVIA administration console or check the deployed modules within your 3DEXPERIENCE environment to verify that the Collaborative Industry Innovator (CII) Document Management component is enabled and accessible to users.Affected if The ENOVIA CII Document Management module is present and active in the environment.
-
Identify accessible document management featuresLog into the 3DEXPERIENCE platform as a standard user and navigate to the Document Management section within ENOVIA CII to determine which document upload, metadata editing, or file management features are available.Affected if Users can upload documents or edit document metadata through the ENOVIA CII interface.
-
Inspect document metadata fields for stored scriptsReview the document metadata schema in ENOVIA CII (for example, title, description, author, or custom attributes) to identify fields that accept user-supplied text and are displayed to other users without output encoding.Affected if Document metadata fields accept freeform text input and are rendered in user browsers without sanitization.
A user is affected if they run 3DEXPERIENCE r2023x through r2025x with the ENOVIA Collaborative Industry Innovator Document Management component enabled, where document metadata fields render user-supplied content without encoding.
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 dataApply vendor patches for affected 3DEXPERIENCE R2023x through R2025x releases and implement output encoding/validation for document metadata display.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2025-10551 — 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-10551 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