CVE-2024-12089
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 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 confidenceA stored Cross-site Scripting (XSS) vulnerability in ENOVIA Collaborative Industry Innovator allows authenticated attackers to inject malicious JavaScript code into application data. This payload executes in the browsers of other users who view the compromised content, enabling session hijacking, credential theft, or defacement.
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>= r2022x, <= 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 installationIdentify whether the 3DEXPERIENCE ENOVIA Collaborative Industry Innovator application is deployed in your environment. Check with your system administrator or review software inventory records.Affected if ENOVIA is not installed in your environment, you are not affected by this CVE.
-
Determine installed versionLocate the installed version of 3ds 3dexperience Enovia. This is typically visible in the application login page, in the About section, or obtainable via administrative console commands. Compare the version number against the affected range: r2022x through r2024x.Affected if Your installed version falls outside the range of r2022x to r2024x, you are not affected. Versions within this range are potentially affected.
-
Verify user authentication is enabledConfirm that user authentication is enabled for ENOVIA. This vulnerability requires an authenticated attacker to inject the malicious payload, so verify whether local user accounts, LDAP integration, or SSO authentication is configured.Affected if Your ENOVIA instance has no authenticated user access (e.g., entirely public with no login capability), the specific attack vector may not apply, though other XSS risks may exist.
-
Identify user-controllable input fieldsReview ENOVIA application data fields where users can create or modify content, such as document metadata, comments, descriptions, or custom attributes. These are the potential injection points for stored XSS.Affected if Users can submit or modify application data fields without output encoding or input validation, the stored XSS vulnerability could be present.
-
Check for output encoding controlsInspect whether the application implements output encoding when displaying user-submitted data to other users. Look for context-appropriate encoding (HTML, URL, JavaScript, or attribute encoding) in the application's presentation layer.Affected if User-submitted data is displayed to other users without proper output encoding or sanitization, you are likely affected by this stored XSS vulnerability.
Your environment is affected if you have ENOVIA Collaborative Industry Innovator installed with a version between r2022x and r2024x, users can authenticate, and user-submitted application data is displayed to other users without proper output 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 3DEXPERIENCE R2022x through R2024x when released. Until then, implement output encoding and strict input validation as compensating controls and restrict user privileges where possible.
- Consultation4.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12089 — 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-2024-12089 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