dbcve.org
3dexperience EnoviaApplication · 3ds

CVE-2024-8004

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
A stored Cross-site Scripting (XSS) vulnerability affecting ENOVIA Collaborative Industry Innovator from Release 3DEXPERIENCE R2022x 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 confidence

Stored Cross-site Scripting (XSS) vulnerability in ENOVIA Collaborative Industry Innovator allows malicious JavaScript to be persisted and executed in victim users' browser sessions. The vulnerability exists in the 3DEXPERIENCE platform from R2022x through R2024x, enabling session hijacking, credential theft, or unauthorized actions performed in the context of authenticated users.

MitigationImplement server-side input validation and output encoding to neutralize malicious script payloads. Apply context-appropriate escaping for all user-supplied data before rendering in HTML, and consider implementing Content Security Policy (CSP) headers as defense-in-depth.

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
3dexperience EnoviaApplication
Affected:= r2022x= r2023x= r2024x

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ENOVIA installation
    Verify that ENOVIA Collaborative Industry Innovator from the 3DEXPERIENCE platform is installed in your environment. This may be visible in your application inventory, system documentation, or by accessing the ENOVIA login portal.
    Affected if ENOVIA is not installed in your environment, you are not affected by this vulnerability.
  2. Identify installed 3DEXPERIENCE version
    Locate the version number of your 3DEXPERIENCE platform installation. This is typically displayed on the login page, in the platform about section, or can be retrieved via system administration tools. Compare your version against the affected range: R2022x, R2023x, or R2024x.
    Affected if Your installed version falls within R2022x through R2024x (inclusive), you are within the affected version range.
  3. Review ENOVIA data model for user-defined fields
    Inspect your ENOVIA data model configuration to identify any custom attributes, widgets, or fields that accept and store user-supplied input. Focus on attributes associated with business objects, documents, or collaborative spaces where users can enter custom text.
    Affected if Custom user-input fields exist in your ENOVIA data model, there is potential for stored XSS exploitation if input validation is insufficient.
  4. Audit output encoding on user-facing forms
    Examine the ENOVIA forms and pages that render stored user data. Check if user-supplied content is displayed back without proper HTML encoding or context-aware escaping. This may require reviewing custom widget configurations or consulting ENOVIA documentation on form rendering.
    Affected if User-supplied data is rendered in HTML contexts without encoding (for example, displaying raw HTML or allowing JavaScript execution in the browser), the stored XSS vulnerability is present.

Your environment is affected if you have ENOVIA Collaborative Industry Innovator installed with a version in the R2022x through R2024x range and your data model or forms allow unencoded user input to be stored and displayed to other users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side input validation and output encoding to neutralize malicious script payloads. Apply context-appropriate escaping for all user-supplied data before rendering in HTML, and consider implementing Content Security Policy (CSP) headers as defense-in-depth.

Fix this in 3dexperience Enovia Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8004 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8004 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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