CVE-2023-1996
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 Release 3DEXPERIENCE R2018x through Release 3DEXPERIENCE R2023x 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 exists in the web interface of Dassault Systèmes 3DEXPERIENCE platform versions R2018x through R2023x. The vulnerability allows execution of arbitrary JavaScript code in the context of a victim's browser via crafted URLs containing malicious script payloads.
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>= r2018x, <= r2023xCVSS 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.
-
Identify the installed 3DEXPERIENCE platform versionAccess the platform administration console or check the version information file typically located in the installation directory. On the server, navigate to the 3DEXPERIENCE installation folder and locate the version manifest or use the platform's built-in version command if available.Affected if The installed version falls within R2018x through R2023x inclusive.
-
Confirm the web interface component is enabledCheck the platform configuration to verify the web-based 3DEXPERIENCE interface is active. This is typically managed through the platform's ENOVIA or 3DSpace web services configuration.Affected if The web interface component is enabled and accessible to users.
-
Locate HTTP endpoints that reflect URL parametersReview the web application's URL patterns and identify endpoints that accept query parameters or path variables. Examine the web server logs or use a browser to test various 3DEXPERIENCE web URLs with test parameter values.Affected if The platform exposes web URLs that reflect user-supplied input back in the HTTP response without proper encoding.
-
Test for reflected input in HTTP responsesSend a crafted request to suspected endpoints using a harmless test string (such as a unique alphanumeric token) as a parameter value, then inspect the response body to see if the exact string appears unencoded in the HTML context.Affected if The response contains the test string verbatim in the HTML output without HTML entity encoding.
You are affected if your installed 3DEXPERIENCE platform version is between R2018x and R2023x and the web interface is enabled, with URL parameters being reflected unencoded in HTTP 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 contextual output encoding for all user-supplied input reflected in HTTP responses and deploy input validation with strict allowlist filtering. Apply vendor patches when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1996 — 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-1996 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