dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9024

HIGH · 8.7 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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 Process Experience Studio in DELMIA Service Process Engineer from Release 3DEXPERIENCE R2024x through Release 3DEXPERIENCE R2026x could allow 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 · high confidence

A stored Cross-site Scripting (XSS) vulnerability exists in Process Experience Studio within DELMIA Service Process Engineer across 3DEXPERIENCE R2024x through R2026x releases. The vulnerability allows malicious script code to be persisted in the application and executed in the context of other users' browser sessions when the stored content is rendered.

MitigationApply vendor-provided patches for the affected 3DEXPERIENCE releases. Until patches are available, implement output encoding and input validation for all user-supplied content rendered by Process Experience Studio.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/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. Verify DELMIA Service Process Engineer installation
    Locate the DELMIA installation directory or check system for Service Process Engineer application files. On Windows, common paths include C:\Program Files\Dassault Systemes\ or check via Add/Remove Programs.
    Affected if DELMIA Service Process Engineer is installed on the system
  2. Identify Process Experience Studio component
    Check for the presence of Process Experience Studio module within the DELMIA installation. Look for folders or files named 'ProcessExperienceStudio', 'ProcessStudio', or similar within the DELMIA directory structure.
    Affected if Process Experience Studio component is present in the installation
  3. Check application version
    Within the DELMIA installation, locate version information - typically in a 'version.xml', 'info.txt', or accessed via the application's About dialog. Compare your version against the affected release timeline for Service Process Engineer.
    Affected if The installed version of Service Process Engineer matches or predates the vulnerable release that contains Process Experience Studio with XSS flaws
  4. Identify web interface or exported content exposure
    Determine if Process Experience Studio is configured to generate web-accessible content, exported documents, or collaborative views where user-created process content is rendered to other users.
    Affected if Process Experience Studio content is exposed via web interface, exports, or shared with other users (stored XSS requires the malicious content to be rendered to victims)
  5. Inspect user content storage and rendering
    Examine the data storage locations where Process Experience Studio saves user-created content. Check how user-supplied process data, annotations, or descriptions are stored and subsequently rendered when accessed by other users.
    Affected if User-supplied content in Process Experience Studio is stored without proper sanitization and rendered to other users without context-aware encoding

A defender is affected if DELMIA Service Process Engineer with Process Experience Studio is installed, the vulnerable component is enabled or exposed to other users, and user-created content can be rendered to victim browsers without output encoding.

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

Apply vendor-provided patches for the affected 3DEXPERIENCE releases. Until patches are available, implement output encoding and input validation for all user-supplied content rendered by Process Experience Studio.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9024 — 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-2026-9024 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