CVE-2025-0833
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 Route Management 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 confidenceA stored Cross-site Scripting (XSS) vulnerability exists in the Route Management component of ENOVIA Collaborative Industry Innovator (part of the 3DEXPERIENCE platform). The flaw allows malicious script code to be persisted within Route Management data, which then executes in the browsers of users who view or interact with the affected route entries. This affects versions R2023x through R2024x.
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.
-
Confirm ENOVIA deploymentIdentify whether the 3DEXPERIENCE platform with ENOVIA Collaborative Industry Innovator is installed in your environment. Check with your system administrator or review software inventory for ENOVIA components.Affected if ENOVIA Collaborative Industry Innovator is present in your environment
-
Check platform versionDetermine the installed version of the 3DEXPERIENCE platform. Compare your version against the affected range: R2023x through R2024x. Consult your platform documentation for version retrieval methods or check with your infrastructure team.Affected if The installed version falls within R2023x through R2024x
-
Verify Route Management accessDetermine whether the Route Management component is accessible to users in your deployment. Check user permissions and role assignments related to Route Management functionality within ENOVIA.Affected if Route Management component is enabled and accessible to users in your environment
-
Inspect Route Management data for suspicious contentReview Route Management entries in your ENOVIA database for any persisted script code, HTML tags, or javascript: URIs that may indicate exploitation. Query the Route Management data tables or use the ENOVIA administration interface to examine stored route definitions.Affected if Stored script code or malicious payloads are found within Route Management data records
You are affected if you have ENOVIA Collaborative Industry Innovator deployed with a version between R2023x and R2024x, and the Route Management component is accessible to users.
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 the vendor-supplied patch for CVE-2025-0833 to the 3DEXPERIENCE platform. Until patched, restrict access to Route Management functionality to trusted users only and implement Content Security Policy headers as a defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0833 — 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-0833 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