CVE-2025-10558
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 3DSearch 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 3DSearch component of 3DSwymer within the 3DEXPERIENCE R2025x release allows malicious script code to be persisted and executed in victims' browser sessions when the stored payload is rendered.
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.
-
Confirm 3DSwymer installationCheck if the 3DSwymer component from 3DEXPERIENCE is installed on the system. Look for 3DSwymer executables or installation directories, or query the system's installed software inventory for '3DSwymer' or '3dswymer'.Affected if 3DSwymer is not installed on the system
-
Verify the exact version is r2025xLocate the 3DSwymer version information. This is typically found in the software's about dialog, installation directory metadata, or via a version query command for the 3DEXPERIENCE platform. Compare the installed version to 'r2025x' exactly.Affected if The installed version is anything other than r2025x
-
Confirm 3DSearch component is in useDetermine whether the 3DSearch functionality within 3DSwymer is enabled or accessible. Check if users have access to the search features provided by the 3DSearch component.Affected if 3DSearch component is not accessible or not in use
-
Inspect for stored XSS payloadsIf 3DSearch is in use, examine any user-created or imported search data, saved searches, or search configuration files for suspicious script tags or JavaScript code patterns. Review the database or file storage where 3DSearch persists user input.Affected if Malicious script code is found persisted in 3DSearch data storage
-
Test 3DSearch input fields for XSSUse the 3DSearch interface to input a benign test script payload (such as <script>alert('test')</script>) into search fields, save the search, and then retrieve/view the saved search to observe if the script executes in the browser context.Affected if The test payload executes or renders as active script code when the stored search is viewed
A system is affected only if 3DSwymer version r2025x is installed AND the 3DSearch component is accessible and contains or permits storage of unescaped script content that renders in users' browsers.
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 proper input validation and output encoding for all user-supplied data in the 3DSearch functionality to prevent script injection.
- 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-2025-10558 — 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-10558 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