CVE-2023-2139
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 reflected Cross-site Scripting (XSS) Vulnerability in DELMIA Apriso Release 2017 through Release 2022 allows an attacker to execute arbitrary script code.
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 reflected Cross-site Scripting (XSS) vulnerability in DELMIA Apriso versions 2017-2022 allows attackers to inject malicious script code through unsanitized user input that is reflected back in server responses. The medium severity (CVSS 6.1) reflects that exploitation requires tricking a user into clicking a crafted link, limiting real-world impact compared to stored XSS.
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>= release_2017, <= release_2022CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate DELMIA Apriso installationCheck the application installation directory or use system inventory tools to find where 3ds Delmia Apriso is installed. Common paths may include C:\Program Files\Dassault Systemes\ or custom installation directories.Affected if DELMIA Apriso is found installed on the system
-
Identify installed versionLook for version information in the application installation folder, such as a version.txt file, or check the application executable properties (right-click on main .exe file, view Details tab for Product Version). Alternatively, check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\DassaultSystemes\Apriso for version keys.Affected if The version displayed cannot be determined or shows a version outside the known format
-
Compare version against affected rangeIf a version string or release number is found, compare it to the affected range: release_2017 through release_2022. For DELMIA Apriso, versions are typically formatted as year-based releases (e.g., 2017, 2018, 2019, 2020, 2021, 2022).Affected if The installed version falls within 2017 through 2022 inclusive
-
Verify application processes user inputSince this is a reflected XSS, confirm the application has functionality that takes user input and reflects it back in server responses (such as search fields, form submissions, or URL parameters). Review application logs or use a test account to submit input and observe if it is reflected in the response.Affected if User-supplied input is reflected back in server responses without sanitization
You are affected if DELMIA Apriso is installed with any version between release_2017 and release_2022 inclusive, and the application reflects user input in responses.
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 output encoding for all user-supplied data displayed in responses and add input validation with strict allowlists on the server side. Consider deploying Content Security Policy (CSP) headers as an additional defense-in-depth measure.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2139 — 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-2023-2139 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