CVE-2024-12090
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 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 confidenceA stored Cross-site Scripting (XSS) vulnerability in ENOVIA Collaborative Industry Innovator R2024x allows attackers to inject malicious JavaScript code into data fields that are persisted in the application. When other users view or interact with the compromised data, the injected script executes within their browser session, potentially stealing session cookies, performing actions on behalf of the user, or redirecting to malicious sites.
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.
-
Identify ENOVIA Collaborative Industry Innovator installationLocate the ENOVIA application in your 3dexperience environment. Check the application installation directory or the 3dexperience platform administration console for installed components.Affected if ENOVIA Collaborative Industry Innovator is present in the environment
-
Confirm the exact version is r2024xAccess the ENOVIA administration interface or system information page. Navigate to Help > About or System > Version Information. Look for the version string r2024x in the installed version details.Affected if The installed version is exactly r2024x (not a later or earlier version)
-
Identify user input fields that persist dataReview ENOVIA data model and business object definitions. Look for customizable data fields, user-defined attributes, or form fields where end users can enter and save custom values into the database.Affected if The application contains user-editable data fields that are persisted to the database
-
Test for lack of input sanitization on stored dataCreate a test user session. Using the ENOVIA web interface, attempt to insert a benign script tag such as <script>alert(1)</script> into a user-editable text field. Save the data, then log out and log in as a different user to view the same record.Affected if The injected script tag executes or renders as HTML when viewed by another user, indicating stored XSS vulnerability
Your environment is affected if ENOVIA Collaborative Industry Innovator version r2024x is installed AND user-editable data fields are present that do not sanitize or encode input before displaying it back 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 dataImplement robust input validation and output encoding for all user-supplied data fields. Additionally, deploy Content Security Policy (CSP) headers and HttpOnly flags on session cookies to mitigate XSS impact.
- 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-12090 — 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-12090 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