dbcve.org
3dexperience EnoviaApplication · 3ds

CVE-2025-10556

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
A stored Cross-site Scripting (XSS) vulnerability affecting Specification Management in ENOVIA Specification Manager from Release 3DEXPERIENCE R2023x through 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 confidence

A stored Cross-site Scripting (XSS) vulnerability exists in the Specification Management feature of ENOVIA Specification Manager across 3DEXPERIENCE R2023x through R2025x releases. Attackers can inject malicious script code into specification fields that persist in the system and execute when other users view the affected content in their browser sessions.

MitigationImplement robust input validation and output encoding on all specification fields within Specification Management; apply context-aware sanitization to neutralize script injection attempts. Until an official vendor patch is available, review existing specifications for malicious content and consider restricting user permissions to specification creation/editing.

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
3dexperience EnoviaApplication
Affected:>= r2023x, <= r2025x

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify ENOVIA version
    Access the 3DEXPERIENCE platform administration console or check the installed ENOVIA version through the platform version information page. Compare the version string against the affected range: R2023x through R2025x.
    Affected if The installed version falls within R2023x to R2025x inclusive.
  2. Confirm Specification Management is active
    Log into ENOVIA and navigate to the Specification Management module. Check whether the feature is accessible and enabled for your user account or globally in the platform.
    Affected if Specification Management feature is enabled and users have access to create or edit specifications.
  3. Inspect specification fields for injected scripts
    Access the Specification Management interface and review existing specifications. Examine all text fields (name, description, attributes, notes) for suspicious patterns such as <script>, javascript:, onerror=, onload=, or other HTML/JS injection vectors.
    Affected if Any specification contains unrecognized or unexpected script tags, event handlers, or encoded JavaScript content.
  4. Review browser execution logs
    Open browser developer tools (F12), navigate to the Console tab while browsing Specification Management pages, and look for any script execution errors, XSS warnings, or unexpected JavaScript behavior.
    Affected if Console displays XSS-related warnings or executes script content from specification fields.
  5. Audit recent specification changes
    Use ENOVIA's audit log or history feature to review recent specifications created or modified, checking for entries containing unusual character patterns or script content.
    Affected if Recent specifications contain suspicious content patterns typical of XSS injection attempts.

Your environment is affected if you are running ENOVIA/3DEXPERIENCE within the R2023x to R2025x version range and the Specification Management feature is accessible to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust input validation and output encoding on all specification fields within Specification Management; apply context-aware sanitization to neutralize script injection attempts. Until an official vendor patch is available, review existing specifications for malicious content and consider restricting user permissions to specification creation/editing.

Fix this in 3dexperience Enovia Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10556 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10556 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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