CVE-2025-0600
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 Product Explorer 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 confidenceStored Cross-site Scripting (XSS) vulnerability in the Product Explorer component of ENOVIA Collaborative Industry Innovator on 3DEXPERIENCE R2024x allows attackers to inject malicious script code that persists and executes in the browser sessions of other users who access the compromised content.
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.
-
Verify ENOVIA 3DEXPERIENCE installationCheck system inventory or installed programs for 'ENOVIA Collaborative Industry Innovator' or '3DEXPERIENCE' with version r2024xAffected if Version is exactly r2024x (or falls within the r2024x release line)
-
Confirm Product Explorer component is activeCheck if Product Explorer module is enabled in the ENOVIA application menu or administration consoleAffected if Product Explorer is accessible and in use by users
-
Review user permissions for Product ExplorerCheck user role assignments in ENOVIA admin to determine which users can create or modify Product Explorer contentAffected if Users with lower trust levels have ability to add content that others view
-
Inspect stored content in Product Explorer for script tagsBrowse Product Explorer data entries or export content to review for unsanitized HTML/JavaScript (script, img onerror, iframe src=javascript:, etc.)Affected if Any stored content contains unescaped script tags or event handlers like onclick, onerror
-
Check for recent unexpected content in Product ExplorerReview activity logs or recent additions in Product Explorer for suspicious entries that may contain encoded or obfuscated script payloadsAffected if New content exists with unusual character sequences typical of XSS attempts
You are affected if ENOVIA Collaborative Industry Innovator r2024x is running with the Product Explorer component enabled and any user-supplied content can be stored and viewed by other users without sanitization.
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 input validation and output encoding on all user-supplied data within Product Explorer; apply contextual output encoding and consider Content Security Policy headers to mitigate XSS execution.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0600 — 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-0600 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