3DSwymer
CVE-2025-10558
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain access to 3DSwymer 3DSearch content field
-
DeliveryStore crafted XSS payload in persisted content
-
ExploitVictim user opens the affected 3DSearch view
-
ExecutionScript executes in victim's authenticated session
-
ImpactHijack session or act as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation targets the 3DSearch feature of Dassault Systèmes 3DSwymer on 3DEXPERIENCE Release R2025x specifically. The attacker must be able to persist a script payload into stored content surfaced by 3DSearch, and successful execution requires a second victim user to load the affected 3DSearch view (UI:R) - it is not a one-shot automatic trigger. Impact is bounded by the browser's same-origin/session context (C:L/I:L, A:N), so it enables session-context script actions rather than direct server compromise. The vendor's PR:N rating implies no authentication is needed to inject, but stored XSS normally requires an account with content-write access; confirm the actual privilege prerequisite with the vendor before treating it as fully unauthenticated. |
| Impact | This is a stored Cross-site Scripting (CWE-79) flaw with a vendor-assigned CVSS 3.1 base score of 6.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) - network vector, low complexity, no privileges, but requiring user interaction, with a scope change and only Low confidentiality and integrity impact. The signals converge on a genuinely medium, not critical, priority: EPSS is 0.20% (9th percentile), indicating very low modeled probability of exploitation; the CVE is NOT on the CISA KEV catalog; and no public exploit (POC) is identified. There is a notable internal tension worth verifying: the vendor rates PR:N (unauthenticated), yet stored XSS normally requires an attacker to place a persistent payload into application-stored content, which in an enterprise collaboration product like 3DSwymer typically presupposes an authenticated account with content-creation rights - the PR:N rating may reflect an unauthenticated injection path (e.g., a publicly writable field) that is not described, so the privilege prerequisite should be confirmed with Dassault Systèmes. The S:C (scope change) correctly captures that injected script executes in the victim's browser authentication context rather than the vulnerable component's. Net assessment: a real but moderate issue - patch within normal cycles; it is a high-UI-dependent, low-impact stored XSS rather than a widespread, automatable threat. |
| Exploit ScenarioDerived | An attacker with access to a content field in the 3DSearch feature of 3DSwymer stores a malicious script payload; when another 3DEXPERIENCE user later views the affected content, the script executes in that victim's authenticated browser session, enabling session-token theft or actions performed as the victim. Exploitation requires the victim to view the poisoned content (UI:R), and no public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Stored cross-site scripting in the 3DSearch feature of Dassault Systèmes 3DSwymer on 3DEXPERIENCE Release R2025x allows an attacker to persist script content that executes in the browser session of a second user who later loads the affected 3DSearch view. The vendor-assigned CVSS 3.1 base score is 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), and our independent assessment shifts the privilege requirement to PR:L, reflecting that stored XSS normally demands an account with content-write access even though the vendor vector claims no privileges. Impact stays within the browser's origin/session context - Low confidentiality and integrity with no availability effect - and there is no public exploit code identified at time of analysis, with EPSS at 0.20% (9th percentile).
RemediationAI
No exact fixed version is stated in the available data, so patch status should be treated as unconfirmed and resolved directly against the vendor advisory at https://www.3ds.com/trust-center/security/security-advisories/cve-2025-10558 - obtain the corrected R2025x build or service pack from Dassault Systèmes and apply it as the primary fix, since no upstream PR or commit reference is provided here. Until that build is confirmed and deployed, the most effective compensating control is to remove the injection precondition: restrict accounts that can create, import, or edit content that 3DSearch indexes, and route such content through a review or moderation step, accepting the trade-off that this constrains collaboration workflows for the affected user groups. If 3DSearch is not business-critical, temporarily disabling or access-restricting the feature eliminates the rendering path entirely at the cost of losing search functionality for those users. Deploy a Content-Security-Policy with a strict script-src (nonce- or hash-based, avoiding unsafe-inline) to blunt execution of persisted payloads, but expect that a platform as script-heavy as 3DEXPERIENCE may require policy tuning or break inline widgets during rollout. Mark session cookies HttpOnly and SameSite=Lax/Strict to prevent script-based cookie theft, noting this does not stop in-session actions performed as the victim. Because exploitation requires a second user to open the affected 3DSearch view, reinforce least-privilege content-write access and user awareness, and monitor web-application and proxy logs for repeated encoded-script patterns in search queries or indexed content as an early indicator.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a CWE-79 improper neutralization of input during web page generation, in its stored (persistent) variant: attacker-supplied data is saved on the platform and later rendered without adequate output encoding by the 3DSearch component, so the payload executes in the origin of the 3DEXPERIENCE web application. CPE data pins the affected build to cpe:2.3:a:3ds:3dswymer:r2025x, i.e. 3DSwymer on the R2025x release train rather than a generic 3DS product. The CVSS vector shows S:C (scope change), which is the standard encoding for XSS where the script runs with the privileges of the hosting site and can act on behalf of the victim beyond the originally vulnerable component, but the impact sub-score remains C:L/I:L/A:N - script-driven session-context actions such as reading exposed page data or performing actions as the victim, not server-side compromise. Exploitation is two-stage: the payload must first be persisted into content indexed or surfaced by 3DSearch, and then a distinct victim must open the affected view (UI:R), so it is not a fire-and-forget automatic trigger. One caveat worth flagging for analysts: the vendor advisory vector lists PR:N while our assessment records PR:L, so the true authentication prerequisite - whether any unauthenticated route can write 3DSearch-indexed content or whether an authenticated content-write account is required - should be confirmed with the vendor before treating this as fully unauthenticated. The very low EPSS score (0.20%, 9th percentile) indicates the model sees negligible near-term exploitation pressure, consistent with a targeted, interaction-dependent enterprise application flaw rather than a mass-exploited one.
Know when 3Dswymer gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Storing a persistent XSS payload in an enterprise collaboration app realistically needs a low-privilege authenticated account (PR:L); victim must view content (UI:R) and script escapes into browser context (S:C), with limited C/I and no availability impact.
Primary rating from NVD.
CVSS VectorNVD
DescriptionNVD
A stored Cross-site Scripting (XSS) vulnerability affecting 3DSearch in 3DSwymer on Release 3DEXPERIENCE R2025x allows an attacker to execute arbitrary script code in user's browser session.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Affected Products (CPE)NVD
Account takeover affects the 3DPassport identity component bundled with Dassault Systèmes 3DSwymer across 3DEXPERIENCE r
Stored cross-site scripting in the 3DSwym social-collaboration module of 3DSwymer on Dassault Systèmes 3DEXPERIENCE R202
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB