CVE-2025-10552
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 3DSwym in 3DSwymer on Release 3DEXPERIENCE R2025x 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 confidenceStored Cross-site Scripting (XSS) vulnerability in the 3DSwym component of 3DSwymer in 3DEXPERIENCE R2025x release. Attackers can inject malicious script code that persists on the server and executes in victim users' browser sessions.
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= r2025xCVSS 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 3DSwymer installation and versionLocate the 3DSwymer installation directory or check the software inventory/version management system for '3dswymer' and confirm the installed version matches r2025x exactly.Affected if The installed version of 3ds 3dswymer is r2025x and the 3DSwym component is in use.
-
Verify 3DSwym component is activeCheck the 3DSwymer configuration or module list to determine whether the 3DSwym component is enabled and accessible to users.Affected if 3DSwym is enabled and users can interact with it.
-
Inspect stored user content in 3DSwymExamine the database or content storage used by 3DSwym for any user-submitted text, comments, profiles, or other fields where input is persisted on the server. Look for HTML script tags, javascript: URIs, or event handler attributes in stored data.Affected if Malicious script code is found persisted in 3DSwym storage, indicating the vulnerability has been exploited.
-
Review Content Security Policy headersCheck HTTP responses from the 3DSwym application for the presence and configuration of Content-Security-Policy headers.Affected if CSP headers are missing or overly permissive, allowing inline script execution.
-
Audit user input fields in 3DSwymIdentify all input forms, text fields, and API endpoints within 3DSwym that accept and store user-supplied data without visible sanitization indicators.Affected if 3DSwym accepts user input that gets stored and displayed back to other users without apparent output encoding.
You are affected if 3DSwymer r2025x is installed with the 3DSwym component enabled and users can submit content that gets stored and rendered without proper encoding.
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 context-aware output encoding and input validation for all user-supplied data in 3DSwym. Apply Content Security Policy headers to mitigate XSS impact.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10552 — 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-2025-10552 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