CVE-2025-0828

8.7 HIGH

📋 TL;DR

A stored Cross-site Scripting (XSS) vulnerability in ENOVIA Product Engineering Specialist allows attackers to inject malicious scripts that execute in users' browsers when viewing compromised content. This affects all users of 3DEXPERIENCE R2022x through R2024x who access the Engineering Release functionality.

💻 Affected Systems

Products:
  • ENOVIA Product Engineering Specialist
Versions: 3DEXPERIENCE R2022x through 3DEXPERIENCE R2024x
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects Engineering Release functionality specifically; requires attacker to have ability to inject malicious content into stored data.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, perform actions as authenticated users, redirect to malicious sites, or install malware through drive-by downloads.

🟠

Likely Case

Session hijacking leading to unauthorized access, data theft, or manipulation of engineering data within the application.

🟢

If Mitigated

Limited impact if proper input validation and output encoding are implemented, though some data exposure may still occur.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires attacker to have some level of access to inject malicious scripts into stored content that other users will view.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for specific patched versions

Vendor Advisory: https://www.3ds.com/vulnerability/advisories

Restart Required: No

Instructions:

1. Review Dassault Systèmes security advisory. 2. Apply the recommended patch or update to a fixed version. 3. Test the update in a non-production environment first. 4. Deploy to production systems.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement strict input validation and output encoding for all user-controllable data in Engineering Release functionality

Content Security Policy

all

Implement Content Security Policy headers to restrict script execution sources

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to detect and block XSS payloads
  • Restrict user permissions to minimize who can create or modify Engineering Release content

🔍 How to Verify

Check if Vulnerable:

Test Engineering Release functionality for XSS vulnerabilities using security testing tools or manual testing with payloads like <script>alert('XSS')</script>

Check Version:

Check application version through ENOVIA/3DEXPERIENCE administration interface or consult system documentation

Verify Fix Applied:

Retest the same functionality after patching to confirm XSS payloads are properly sanitized and no longer execute

📡 Detection & Monitoring

Log Indicators:

  • Unusual content submissions containing script tags or JavaScript code in Engineering Release data
  • Multiple failed login attempts following suspicious content submissions

Network Indicators:

  • Outbound connections to unexpected domains following user interaction with Engineering Release content
  • Unusual data exfiltration patterns

SIEM Query:

source="enovia_logs" AND ("<script>" OR "javascript:" OR "onerror=" OR "onload=") AND "Engineering Release"

🔗 References

📤 Share & Export